Telecommunication Management Network, TMN*

*Mani Subramanian “Network Management: Principles and practice”, Addison-Wesley, 2000.

Background

Based on OSI CMIP/CMIS Address the interoperability of multi-

vendor equipment used by different service providers and define standard interfaces

Provide a framework for telecommunications network and service management Management goes beyond networks and

network element to include managing services provided by service providers as well as business management

Trends In Telecommunications Globalizations and

Deregulation End-to-end service involves

multiple providers• Demand for standards

based network and service management (interoperability)

Merge of telecom and datacom

Need for Inter-working between management protocols to provide end-to-end management

Evolution in protocolso Need for flexible management

architecture

Competition Time-to market for new

services• Need for sound (flexible)

architecture Focus on customer care (i.e.,

service quality) Decreasing margins (do

more with less)• Increase revenue

(providing high quality services) while minimizing network operation costs

Example of Management (1)

Telecommunication Network

Figure 11.1 Operations System for Network Transmission

Public Switch

TransmissionTest System

TransmissionTest System

Public Switch

TrunkTest System

Voice Voice

Nodes

Transmission Links

Trunk Testing System Trunk is a logical

connection between two switching nodes

Periodic measurement of loss and S/N of all trunks

Failing threshold set for QoS; failing trunks removed out of service before the customer complains

Example of Management (2)

Telephone Switch Traffic Traffic monitored at

switch appearance Call blocking statistics

obtained Traffic and call-blocking

statistics provide data for planning

Importance of Operations, administration, mainte- nance, and provisioning

Figure 11.2 Operations System for Traffic Measurement

Data / Telecommunication Network

Router / Switch

TrafficCounter

TrafficCounter

Router / Switch

TrafficMeasurement System

Transmission Links

Nodes

TMN Conceptual Model

TMN is conceptually a separate network Interfaces between the TMN and the Telecommunication network are formed by exchanges

and transmission switches OSs (Operations Systems) perform most of the management functions and they are

connected to TMN through a Data Communication Network (DCN) The DCN is used to exchange management information between OSs

TMN Objectives

The basic concept behind a TMN is to: provide an organized

architecture to achieve the interconnection between various types of OS’s and/or telecommunications equipment for the exchange of management information using an agreed architecture with standardized interfaces including protocols and messages

The M.3010 recommendation defines “general architectural requirements for a TMN to support the management requirements of administration to plan, provision, install, maintain, operate and administer telecommunication networks and services”

TMN Management Architectures

Functional Architecture Describes a number of management functions (control,

monitor, etc.)

Physical Architecture Defines how management functions are implemented into

physical equipment Information Architecture

Describes concepts that have been adopted from OSI management

Logical Layer Architecture A model that shows how management can be

structured according to different responsibilities

TMN Functional Architecture The TMN functional architecture explains the

distribution of functionality within a TMN The TMN functional architecture is defined by:

TMN function blocks, being the roles in which functions operate (coordinate, mediate, etc.)

TMN function points, being the service boundary between two communication management function blocks

TMN Functional Architecture Interfaces between function blocks are defined as

reference points

q class between OSF, QAF, MF and NEFf class for attachment of a WSFx class between OSFs of two TMNs or between TMN OSF and OSF-like function in other networkg class between WSF and usersm class between QAF and non-TMN managed entities

TMN Functional Architecture Network Element Function, NEF:

o Exchanges, transmission systems, switches, etc.o NEs are subject to management and support the exchange of

data between userso They include management functions (i.e., agents)

Operation Systems Functions, OSF:o Operations and Notificationso Within a TMN, multiple OSFs may exist and they

communicate through q3 interfaceo OSFs belonging to different administrative domains may also

communicate through x reference point

CMIPCMIS

TMN Functional Architecture Work Station Function, WSF

o Interprets management information to a human user through g interface

Q Adapter Function, QAFo Non TMN entities (e.g. proprietary) can be

connected to a TMN entityo Translate between q reference point and m

reference point (similar to a proxy agent in SNMP)

TMN Functional Architecture Mediation Function (MF)

o Located within the TMNo Operations on the information between network

elements; e.g. storage, filtering, threshold detection, etc.

o MF can be shared between multiple OSSs; e.g. RMON

TMN Functional Architecture Data Communication Function (DCF)

o Provide the necessary physical connection with various network components

o DCF implements layers 1-3 of OSIo Connect NEs, QAs, and MDs to the OSs at the

standard q interfaceo Connect MDs to NEs and QAs using q interface

TMN Physical Architecture

OperationsSystem

(OS)

Data Communications Network (DCN)

Q Adapter(QA)

Data Communications Network (DCN)

NetworkElement

(NE)

Q Adapter(QA)

NetworkElement

(NE)

MediationDevice(MD)

X/F/Q3

F/Q3

Qx

Q3

Q3

QxQx

X

F

TMN

Workstation

OperationsSystem

(OS)

TMN Information Architecture

TMN makes use of OSI Systems Management principles and is based on an object-oriented paradigm.

Management systems exchange information modeled in terms of managed objects (MO)

A managed object (MO) is defined by:o the attributes visible at its boundaryo the management operations which may be applied to ito The behavior exhibited by it in response to management

operations or in reaction to other types of stimuli (e.g., threshold crossing)

o The notifications emitted by it

TMN Information Architecture

MCF

MCF

R R

R

Agentmanagementoperations

notifications

Q I/F

applicationfunctions

TMN

MCF: Message Communication FunctionR: Network Resource to be managed

Manager

Information Model based on Object-Oriented Approach

MIT: dynamic structure, unlike MIB which is static

OSI System Architecture

OSI System Architecture

OSI ManagerApplication

M-G

ET

M S

ET

OSI Manager

Application Entity

Presentation (ITU Recommendation X.216 and X.226)

Session (ITU Recommendation X.215 and X.225)

Transport (ITU Recommendation 224)

Network (x.25)

OSI Agent

PHY

Physical Medium

Manage-mentData

M A

CT

ION

M-E

VE

NT

-RE

PO

RT

M-C

RE

AT

E

M-D

EL

ET

E

M-C

AN

CE

L-G

ET

DLC

OSI AgentApplication

M-G

ET

M S

ET

Application Entity

Presentation (ITU Recommendation X.216 and X.226)

Session (ITU Recommendation X.215 and X.225)

Transport (ITU Recommendation 224)

Network (x.25)

PHY

M A

CT

ION

M-E

VE

NT

-RE

PO

RT

M-C

RE

AT

E

M-D

EL

ET

E

M-C

AN

CE

L-G

ET

DLC

OSI System Architecture

ManagingProcess

AgentProcess

CMISECMIP CMISE

lower layers

lower layers

ManagementFunction

OSI System ArchitectureM-GET

Used to retrieve the values of one or more attributes of one or more MOsScoping/Filtering, Linked Replies and SynchronizationConfirmed service only

M-SETUsed to replace the values of one or more attributes of one or more MOsScoping/Filtering, Linked Replies and SynchronizationMay be Confirmed or Unconfirmed

M-ACTIONConveys Object Class/Instance, Action Type and optional action-specific informationMeaning dependent on MO action specificationScoping/Filtering, Linked Replies and SynchronizationMay be Confirmed or Unconfirmed

OSI System Architecture

M-CANCEL-GETPermits a linked GET response to be terminatedConfirmed service only

M-EVENT-REPORTConveys Object Class/Instance, Event Type and optional event-specific informationMeaning dependent on MO notification specificationMay be Confirmed or Unconfirmed

M-CREATEPermits creation of new instances of object classesPermits specification of default values (of attributes, explicitly and/or by reference)Permits explicit or automatic instance namingConfirmed service only

M-DELETEPermits deletion of object class instancesScoping/Filtering, Linked Replies and SynchronizationConfirmed service only

OSI Communication Model

System-management application-service element(SMASE)

Common management information service element(CMISE)

Presentation layer

Association-control-serviceelement (ACSE)

Remote-operations-serviceelement (ROSE)

A-Associate A-ReleaseA-Abort

A-Associate A-ReleaseA-Abort

M-EVENT-REPORT M-GET M-SET M-ACTION M-CREATE M-DELETE M-CALCEL-GET

RO-Invoke RO-Reject RO-Result RO-Error

P-Connect P-Release P-Abort P-Data

Application process

SMASE services the following applications:

Configuration ManagementFault ManagementPerformance ManagementSecurity ManagementAccounting Management

handles the communication functions of SMASE using CMIP

Setup and coordinate the activities or setting up/releasing association with the application

Once association is setup, data moves from CMISE to the remote system via ROSE

OSI Communication Model

A selection function to locate MO record accessed by Get/Set/Action of CMISE

OSI Information Model A managed object (MO) is

defined in terms of: attributes it possesses operations that may be

performed upon it notifications that it may

issue its relationships with other

MOs

A managed-object class is a model or template for MO instances that share the same attributes, notifications, operations and behavior

A MO class can be created from other MO classes (called packages)

Managed Object Class

Conditional PackageAttributesBehavior

OperationsNotifications

Mandatory PackageAttributesBehavior

OperationsNotifications

Conditional PackageAttributesBehavior

OperationsNotifications

A MO has the properties associated with the mandatory package and may include properties of conditional packages

MO classes are obtained by using an inheritance tree

Other trees are: naming tree and registration tree

OSI Information Model

Hub Managed Object Class

hub idvendor name

model numberserial number

number of interfacestype of interfaces

speed of interfaces

Hub1 Instance

hub id = “Hub1”vendor name = “ABC”model number =“abc”serial number = “123”

number of interfaces = 12type of interfaces = 6

speed of interfaces = 10000000

Hub2 Instance

hub id = “Hub2”vendor name = “XYZ”model number =“xyz”serial number = “456”

number of interfaces = 12type of interfaces = 6

speed of interfaces = 10000000

Managed Object Class and Instances

OSI Information Model

Switched hub

Routers hub

Regularhub

Switched100-Mbps

Hub

Top

Switched10-Mbps

Hub

10-MbpsRegular

Hub

SwitchedMultirate

Hub

10-MbpsUni-LAN

Hub

Superclass vs. subclass Attributes of a Superclass are

maintained by a subclass and more are possibly added

Single inheritance, multiple inheritance (polymorphic),

o A subclass derives its property from more than one superclass

and allmorphico A subclass derived from multiple

superclasses takes the properties of one superclass

OSI Information Model

GDMO: Guidelines for Definition of Managed Object Templates

o Extensions to ASN.1 to handle the syntax of managed information definition

o Template (similar to ASN.1 Macro) is introduced to combine definitions

MO name Specifies a superclassMandatory package and properties

Official registered name of the object class under the ISO registration tree

Templates used to combine definitions of attributes,operations and notifications

OSI vs. SNMPOSI Mgmt (CMIP) Internet Mgmt (SNMP)

InformationModel

Object-Oriented Scalar

MIB Language GDMO SNMP SMI

Mgmt Entity Interactions

Manager-Agent,Manager-Manager

Manager-Agent,Manager-Manager

ProtocolOperations

M-Get, M-Set, M-ActionM-Create, M-DeleteM-Event-Report

Get, Setlimited Create/DeleteTrap

MO AddressingMIT with OID Scoping/Filtering

MIT with OID at leaves of the tree

ManagementApplications Five Functional Areas Not Specified

StandardizationBody

ITU-T, ISO IETF

Features

OSI vs. SNMP

OSI management uses connection-oriented transport and confirmed interactions. (reliability and bulk retrieval)

They require, however, complex communication environment and result in failure-sensitivity.

During network stress time, connections may not be sustainable over sufficiently long time to accomplish the management functions needed.

Management entities may need to spend significant time and resources in handling lost connections.

Connection-based transport may become an obstacle in accomplishing management interactions at a time when they are needed most

SNMP communications use a connectionless datagram transport (UDP) with confirmed GET/SET interactions and unconfirmed event notifications (TRAPs).

The responsibility to ensure reliable communications is passed to agent/manager applications.

During stress time, managers may flexibly adjust their computations to handle loss

A datagram model requires a simple communication environment that is easy to implement. Managers, however, can only retrieve information that fits within a single UDP frame. This limits bulk retrieval mechanisms.

Relation between TMN and OSI

Reference points interconnect different function block comparable to underlying service providers

TMN Information Architecture

M A M A

Resource ResourceResourceResource

system A system B system C

MIB MIBseessees

CMIP CMIP

CMIS CMIS CMISCMIS

Information Model B

Information Model c

OSIprotocol stack

OSIprotocol stack

* CMIP: Common Management Information Protocol * MIB: Management Information Base* CMIS: Common Management Information System

Manager/Agent InterworkingManager/Agent Interworking

Management Service Architecture

Vendor dependent

Management Service Architecture

Network Element Layer, NELo Comprise NEs such as switches, routers, transmission

facilitieso Managed by the OSFs residing in the element management

layer Element Management Layer, EML

o It deals with vendor specific management functions and hide these functions from the layer above

o Functions performed:o Detection of equipment errorso Measuring power consumption and the temperature of

equipmento Measuring resource usage: CPU, shared buffer, queue

length, etc.o Logging of statistical datao Etc..

o NOTE: OSF in the element management layer and NEF may be implemented in the same piece of equipment

Management Service Architecture

Network Management Layer, NMLo Managed functions related to interaction between multiple

pieces of equipment (i.e., managing a network)o Internal structure of network elements is not visible (they are

vendor specific)o Functions performed:

o Create the complete network viewo Setup/provisioning dedicated paths (with QoS parameters)

for end users through the network o Modifying routing tableo Monitoring link utilizationo Optimizing performanceo Fault detection

o The OSFs in NML interacts with the OSFs at the EML: it uses information provided by the EML to implement its functions

o Here OSFs in NML acts as a manager and OSFs at EML acts as an agent

Management Service Architecture

Service Management Layer, SMLo Manage services provided by the network and seen by

userso Users may be end users (customers) and/or service providers

using the telecommunication networko Relies on management information provided by the

Network Management Layer (NML)o The internal structure of the network (i.e., network details)

are hiddeno Functions performed:

o QoS management (delay, jitter, etc)o Accounting/billingo Addition/removal of users, etc..

o Example: inter-operator managemento Two interconnected networks may exchange management

information (e.g., necessary for QoS negotiation) but both network operators keep their network structure hidden from each other, (Proprietary).

Management Service Architecture

Service Management Layer, Exampleo A transport network (e.g., ATM, SONET or WDM) that

is used by service providers to connect end routers and provide services

Border OXC

Border OXC

Core OXCCore OXC

IP Border Router

IP Border Router

UNI

Client/Server ModelClient/Server Model

Management Service Architecture

Two independent control planes isolated from each other

o The IP routing, topology distribution, and signaling protocols are independent of the ones at the Optical Layer

Routers are clients of optical domaino The Optical Networks provides wavelength path to the

electronic clients (IP routers, ATM switches)

Optical topology invisible to routers

Standard network interfaces are required such as UNI and NNI

?Black Box for IP networks

Management Service Architecture

Management Service Architecture

Example IP over ATM exampleo IP service provider connects to the ATM provider through X-

reference pointso The details of the ATM backbone are hidden from the IP service

providero IP provider is not allowed to monitor/modify/etc. internal

equipment of the ATM backbone; rather, only high level information is communicated, such as QoS figures!

o An ATM link is considered as a single element for the IP network, therefore the reference point at the EML of IP

o Another reference point at the IP NML:o Allows for fault detection, rerouting, load balancing,

optimization, etc..o Finally, the IP network should monitor the ATM links for any

degradation in network performance that may impact the QoS of the IP provider:

o Therefore another reference point at the service management layer

Management Service Architecture

Business Management Layer, BMLo Includes all the functions necessary for the

implementation of policies and strategies within the organization which owns and operates the services (and possibly the network)

o interacts with the service management layero Is influenced by high levels of control such as

legislation or macro-economic factors (e.g., tariffing policies, quality maintenance strategies)

TMN vs. Internet Management TMN focuses on the specifications of management

architectures whereas Internet focuses on the implementation of management protocols.

Integration between TMN and SNMP is obtained through Q Adapter Function (QAF)

o QAF translates between q3 (OSI CMIP) reference point and m reference point (SNMP)

o QAF: Translating between OSI GDMO (Guidelines for the Definition of Managed Objects) and SNMP SMI is a critical task

TMN (unlike Internet management) defines a separate Network to exchange management information: that is the DCN. (TMN is this sense resembles SS7 network)

Internet Service management: Internet needs to be extended to allow exchange of management information between different operators..

Separating the Management from TN

Prevent potential problems with fault management:

o In case of failures, failed component may still be accessed through the separate management network

o OSI and SNMP have collapsed management/data network

o A separate management network requires additional equipment and transmission systems costs are higher! It may also require a separate network to manage the management network (meta management)

o Telecommunication networks (e.g., telephony network) cannot/does not rely on asynchronous type of service provided by the data networks a separate management network for TN is essential

o OSI and SNMP are aimed toward data networks: therefore, the advantages of having a separate network for management should be weighed vs. the cost incurred by adding an additional separate network