Telecommunications Network - Network Management Architecture

TMN (Telecommunications Management Network) is an ITU standard which defines a Network Management Architecture. (see also OMNIPoint, X.700, etc).

Originally most standards defined the interface to the customer, network management standards define internal workings of the network. The effect should be to allow us and our competitors to mix network elements from different manufacturers and buy off the shelf management systems to manage them all. In other words to be systems integrators and to add value on top of that.

The TMN is the architecture currently accepted by the industry and therefore if we want to buy off the shelf management systems then we have to use this architecture.


TMN Architecture - Segmentation

Business Management

It seems to me that Business Management Systems are less closely coupled to the network and more linked to the business process such as HOMS, FMS, NESS and NBS. If we loose these systems there may not be an immediate effect on customers unless they have a fault or wish to change their service. The middle column are more tightly coupled to the physical network and more realtime, such as polling, monitoring alarms, displaying network status, checking customers configuration, monitoring protocols, loading configuration changes, etc.

Examples of Business Management issues:

Systems Requirements

Work Tracking

Billing & Reconciliation (no usage billing yet)

Support for Helpdesk, Trouble Ticket, etc

Element Management

In some cases router management is done by individually configuring and faultfinding each box. This is very inefficient and needs lots of highly skilled people with a detailed knowledge of the network.

Examples of Element Management issues:

System Requirements:

Network Management

This is the level of management that we have on our X.25 networks, although this is based on proprietary and DIY systems.

Examples of Network Management issues:

System Requirements:

Service Management

This it the management of the end-to-end service regardless of what networks the service goes through and needs a knowledge of virtual network such as what terminals connect to what hosts. Customer stats, monitoring QOS and contract terms.

Examples of Service Management issues:

System Requirements:



metadata block
see also:


Correspondence about this page

Book Shop - Further reading.

Where I can, I have put links to Amazon for books that are relevant to the subject, click on the appropriate country flag to get more details of the book or to buy it from them.

cover OSI Reference Model for Telecommunications (McGraw-Hill Telecom Professional S.)

Commercial Software Shop

Where I can, I have put links to Amazon for commercial software, not directly related to the software project, but related to the subject being discussed, click on the appropriate country flag to get more details of the software or to buy it from them.

cover US Robotics Sureconnect ADSL Micro Filter.

This site may have errors. Don't use for critical systems.

Copyright (c) 1998-2015 Martin John Baker - All rights reserved - privacy policy.