UNIVERSITY OF TWENTE

E

CHES

CopThes

The SimpleWeb

INTRODUCTION TO TMN

BACKGROUND

STANDARDS

ARCHITECTURES• FUNCTIONAL ARCHITECTURE

• PHYSICAL ARCHITECTURE• INFORMATION ARCHITECTURE

• LOGICAL LAYERED ARCHITECTUR

RELATION TO OTHER APPROA• ISO-OSI• SNMP

yright © 1999 by Aiko Prase sheets may be used for educational purposes

UNIVERSITY OF TWENTE

ORK

NT

HY CONCEPT

The SimpleWeb

BACKGROUND

TELECOMMUNICATIONS MANAGEMENT NETW

ITU-T

DEFINITION STARTED 1985

DEFINED IN M-SERIES• M.3010

USES OSI SYSTEMS MANAGEME

FAMOUS FOR ITS MANAGEMENT HIERARC

UNIVERSITY OF TWENTE

rations

stem

WorkStation

Exchange

The SimpleWeb

STRUCTURE

Operations

System

Operations

System

Telecommunication network

TMN

Ope

Sy

ExchangeTransmission

systemsExchange

Transmission

systems

Data Communication Network

UNIVERSITY OF TWENTE

NUMBER DATE

M.3000 10/94

M.3010 05/96

M.3020 07/95

M.3100 07/95

M.3101 07/95

M.3180 10/92

M.3200 10/92

M.3207.1 05/96

M.3211.1 05/96

M.3300 10/92

M.3320 04/97

M.3400 04/97

The SimpleWeb

STANDARDS

TITLE

Overview of TMN Recommendations

Principles for a TMN

TMN interface specification methodology

Generic network information model

Managed object conformance statements for the generic network inf. model

Catalogue of TMN management information

TMN Management Services: Overview

TMN management Services: Maintenance aspects of B-ISDN management

TMN management Services: Fault and performance mgt. of the ISDN access

TMN management capabilities presented at the F interface

Management requirements framework for the TMN X-interface

TMN management functions

UNIVERSITY OF TWENTE

TMN managementcapabilities at the

X interface: M.3320

rms and definitionsTMN

M.60 §2

t

MN managementapabilities at the interface: M.3300

The SimpleWeb

STANDARDS: RELATIONSHIP

Management service n*

Overview ofTMN Recommendations

M.3000

TePrinciples for aTMN

M.3010

TMN interfacespecification methodology

M.3020

TMN managemenfunctionsM.3400

Generic network informationmodel for TMN

M.3100

Catalogue of TMNmanagement information

M.3180

Management service 1*

TMN managementservices: overview

M.3200

Tc

F

UNIVERSITY OF TWENTE

NUMBER DATE

M.3600 10/92

M.3602 10/92

M.3603 10/92

M.3604 10/92

M.3605 10/92

M.3610 05/96

M.3611 04/97

M.3620 10/92

M.3621 07/95

M.3640 10/92

er of M.3641 10/94

M.3650 04/97

M.3660 10/92

The SimpleWeb

STANDARDS: ISDN

TITLE

Principles for the management of ISDNs

Application of maintenance principles to ISDN subscriber installations

Application of maintenance principles to ISDN basic rate access

Application of maintenance principles to ISDN primary rate access

Application of maintenance principles to static multiplexed basic rate access

Principles for applying the TMN concept to the management of B-ISDN

Test management of the B-ISDN ATM layer using the TMN

Principles for the use of ISDN test calls, systems and responders

Integrated management of the ISDN customer access

Management of the D-channel - Data link layer and network layer

Management information model for the management of the data link and network laythe ISDN D channel

Network performance measurements of ISDN calls

ISDN interface management services

UNIVERSITY OF TWENTE

E

RE

The SimpleWeb

ARCHITECTURES

• FUNCTIONAL ARCHITECTURE

• PHYSICAL ARCHITECTURE

• INFORMATION ARCHITECTUR

• LOGICAL LAYERED ARCHITECTU

UNIVERSITY OF TWENTE

on blocks:ns System Functions Functions

tation Functions Element Functionstor Functions

The SimpleWeb

FUNCTIONAL ARCHITECTURE

MF

TMN

OSF

TMN FunctiOSF = OperatioMF = MediationWSF = Work SNEF = NetworkQAF = Q Adap

NEF

WSF

QAF

UNIVERSITY OF TWENTE

LE

g

= reference point

WSF

The SimpleWeb

FUNCTIONAL ARCHITECTURE - EXAMP

TMN

f

m

q q

q

x

TMN

OSF

MF

NEFQAF

OSF

UNIVERSITY OF TWENTE

)

The SimpleWeb

OSF AND NEF

q3

NEF

OSF OSI (CMIP

UNIVERSITY OF TWENTE

F

The SimpleWeb

MEDIATION FUNCTIONS

q3

qx

BETWEEN NEF AND OSF BETWEEN QAF AND OS

q3

qx

NEF

MF

OSF

QAF

MF

OSF

UNIVERSITY OF TWENTE

meference

pointnon-TMN

NEF

The SimpleWeb

Q ADAPTOR FUNCTIONS

mreference

point

qreference

point

TMNnon-TMN

OSF QAF

rq

referencepoint

TMN QAF

UNIVERSITY OF TWENTE

KS

WSF Non-TMN

f

f

m

m

g**

g**

SF is in a different TMNF and the human user

The SimpleWeb

RELATION BETWEEN FUNCTION BLOC

NEF

OSF

MF

QAFq3

QAFqx

WSF

Non-TMN

NEF OSF MF QAFq3 QAFqx

q3 qx

q3 x*, q3 q3 q3

qx q3 qx qx

q3

qx

f f

m m

m, g = non TMN reference points* = x reference point only applies when each O** = The g reference point lies between the WS

UNIVERSITY OF TWENTE

NCTION

NCTION

NCTION

NCTION

NCTION

TION

TION

The SimpleWeb

FUNCTIONAL COMPONENTS

• MAF: MANAGEMENT APPLICATION FU

• ICF: INFORMATION CONVERSION FU

• WSSF: WORKSTATION SUPPORT FU

• UISF: USER INTERFACE SUPPORT FU

• MCF: MESSAGE COMMUNICATION FU

• DSF: DIRECTORY SYSTEM FUNC

• DAF: DIRECTORY ACCESS FUNC

• SF: SECURITY FUNCTION

UNIVERSITY OF TWENTE

NENTS

TMN

FUNCTIONAL

COMPONENTSF

NCTION BLOCK

The SimpleWeb

FUNCTION BLOCKS & FUNCTIONAL COMPO

TMN

FUNCTIONAL

COMPONENTSMCF

DCF

MC

PEER TO PEER COMMUNICATION

FUFUNCTION BLOCK

UNIVERSITY OF TWENTE

AL COMPONENTS

DAF SF

O O

O O

O O

O O

O O

O O

O O

ay be inconflict with ISO definitions

The SimpleWeb

MAPPING BETWEEN FUNCTION BLOCKS & FUNCTION

OSF

WSF

NEF q3

NEF qx

MF

QAF q 3

QAF q x

MAF1 ICF WSSF UISF DSF

M O O O

2 2 M

M O

O O

O M O O

O M O

O M O

1: MAF is considered to be additional to any Agent or Manager activities and m2: These functions (or equivalent) may be considered to be as part of the UISF

UNIVERSITY OF TWENTE

AGEMENT FUNCTIONS

MANAGEMENTED INTO

The SimpleWeb

PHYSICAL ARCHITECTURE

FUNCTIONAL ARCHITECTURE DEFINES THE VARIOUS TMN MAN

DEFINES HOW THE VARIOUS TMNFUNCTIONS CAN BE IMPLEMENTPHYSICAL EQUIPMENT

PHYSICAL ARCHITECTURE

UNIVERSITY OF TWENTE

CTURE

REFERENCE POINTS

INTERFACES

The SimpleWeb

FUNCTIONAL VERSUS PHYSICAL ARCHITE

FUNCTIONAL COMPONENTS

FUNCTION BLOCKS

PHYSICAL EQUIPMENT

TMN FUNCTIONAL ARCHITECTURE:

TMN PHYSICAL ARCHITECTURE:

+

(BUILDING BLOCKS)

UNIVERSITY OF TWENTE

OCKS

F

*

ndatorytionaly only be presentSF or MF is also present

The SimpleWeb

FUNCTION BLOCKS VERSUS BUIDING BL

MD

OS

QA

WS

NEF

M

MF

O

M

O

QAF

O

O

O

M

OSF

O

O

M

WS

O

O

O

M

NE

M = MaO = OpO* = ma

if O

DCN

UNIVERSITY OF TWENTE

CES

(g m)

TION BLOCK

ING BLOCK

The SimpleWeb

REFERENCE POINTS VERSUS INTERFA

REFERENCE POINT:

INTERFACE:

qx

Qx

q3

Q3

x

X

f

F

REFERENCE POINT

INTERFACE

FUNC

BUILD

DRAWING CONVENTIONS:

UNIVERSITY OF TWENTE

E

= INTERFACE

WS

The SimpleWeb

PHYSICAL ARCHITECTURE - EXAMPL

X/F/Q3

Q3/F

QxQ3Q3

QxQx

F

X

TMN OS

MD

NEQA NE QA

DCN

DCN

UNIVERSITY OF TWENTE

CATIONS

The SimpleWeb

INFORMATION ARCHITECTURE

MANAGED OBJECT

ATTRIBUTESOPERATIONS NOTIFI&

BEHAVIOUR

UNIVERSITY OF TWENTE

RE

ER

T

The SimpleWeb

LOGICAL LAYERED ARCHITECTU

MANAGER

AGENT MANAG

AGEN

LAYER 1

LAYER 2

LAYER 3

UNIVERSITY OF TWENTE

The SimpleWeb

FUNCTIONAL HIERARCHY

BUSINESSMANAGEMENT LAYER

SERVICEMANAGEMENT LAYER

NETWORKMANAGEMENT LAYER

ELEMENTMANAGEMENT LAYER

NETWORKELEMENT LAYER

X

X

X

Q3

Q3

Q3

Q3

NEF

OSF

OSF

OSF

OSF

UNIVERSITY OF TWENTE

T

ANAGEMENT

TS

The SimpleWeb

BT’s RESPONSIBILITY MODEL

BUSINESS MANAGEMENT

SERVICE MANAGEMENT

NETWORK MANAGEMEN

NETWORK ELEMENT M

NETWORK ELEMEN

UNIVERSITY OF TWENTE

ROVIDER TMNTRANSPORT PROVIDER)

OSF

OSF

OSF

OSF

NEF

The SimpleWeb

EXAMPLE: ISP WHO USES ATM LINKS

SERVICEMANAGEMENT LAYER

NETWORKMANAGEMENT LAYER

NETWORK ELEMENTLAYER

BUSINESSMANAGEMENT LAYER

x

P

ELEMENTMANAGEMENT LAYER

(E.G. ATM CUSTOMER TMN

(IP SERVICE PROVIDER)

x

x

NEF

OSF

OSF

OSF

OSF

UNIVERSITY OF TWENTE

q

ervice Provider

OSF

OSF

The SimpleWeb

EXAMPLE: VALUE ADDED SERVICES

SERVICEMANAGEMENT LAYER

NETWORKMANAGEMENT LAYER

ELEMENT

MANAGEMENT LAYER

NETWORK ELEMENTLAYER

BUSINESSMANAGEMENT LAYER

x

SValue AddedService Provider

TMN1

TMN2

NEF

OSF

OSF

OSFOSF

OSF OSF

UNIVERSITY OF TWENTE

DS

ONCEPT

MODEL)

The SimpleWeb

RELATION WITH ISO-OSI

REFERENCE TOISO MANAGEMENT STANDAR

• SAME VIEW OF MANAGER-AGENT C

• SAME OO APPROACH

• SAME MANAGEMENT INFORMATION(INFORMATION ARCHITECTURE

• SAME PROTOCOLS(CMIP)

UNIVERSITY OF TWENTE

PROTOCOL

ENTITY - C

PROVIDER Y

C

The SimpleWeb

TMN VERSUS OSI CONCEPTS

PROTOCOL

ENTITY - B

PROTOCOL

ENTITY - A

SERVICESERVICE PROVIDER X

X Y

TMN:

OSI:

A B

UNIVERSITY OF TWENTE

& NEF

NEF(AGENT)

The SimpleWeb

TMN VERSUS OSI CONCEPTS: OSF

OSF(MANAGER)

q3 REFERENCE POINT

UNIVERSITY OF TWENTE

MENT

NMENT

The SimpleWeb

RELATION WITH SNMP

q3

m

SNMPAGENT

TMN ENVIRON

SNMP ENVIRO

QAF

OSF