1. Telecommunication Network Managementtmn management architecture Khalid Ibrahim Qureshi - Dept. of Computer Science CIIT - Wah

2. TMN Introduction • Telecommunications Management Network (TMN) provides a framework for achieving interconnectivity and communication across heterogeneous operating systems and telecommunication networks. • ITU-T TMN defines only management architecture and rely heavily on OSI management framework using OSI protocols CMIP/CMIS. • TMN management architecture provides out-of-band management. Management information flows on a separate network that is used solely for network management purposes (DCN). DCN interfaces with telecommunications equipment to control its operations. • TMN service management architecture provides an environment for different service management functions (TMN FCAPS) and different management domains (SML, NML and EML) • TMN was developed by ITU-T in 1988 as an infrastructure to support management and deployment of dynamic telecommunication services. • TMN was intended mainly for PSTNs but can be used in the management of ISDN, B-ISDN, ATM, and GSM networks.

3. TMN Architecture

4. TMN Architecture

5. Operations System (OS) • OS is the TMN “Supervisory” & “Control” System • Operations System (OS) or Operation Support System (OSS) is a system that performs the functions that support processing of information related to operations, administration, maintenance, and provisioning (OAM&P) and FCAPS for the networks, including surveillance and testing functions to support customer access maintenance. • TMN Management Layers / Domains : • – Business / (Application) Management • – Service Management • – Network Management • – Element Management

6. FCAPS and Domains/Layers

7. TMN Management Layers / Domains

8. TMN Layered Architecture

9. TMN System Components • 1. Operations System (OS): OS performs operations system functions, including operations monitoring and controlling telecommunications management functions; the OS can also provide some of the mediation, q-adaption, and WS functions. • 2. Mediation Device (MD) MD performs mediation between local and the OS information model; mediation function may be needed to ensure that the information, scope, and functionality are presented in the exact way that the OS expects. Mediation functions can be implemented across hierarchies of cascaded MDs.

10. TMN System Components • 3. Q-Adapter The QA enables the TMN to manage NEs that have non-TMN interfaces. The QA translates between TMN and non-TMN interfaces. A TL1 Q-adapter, for example, translates between a TL1 ASCII message-based protocol and the CMIP , the TMN interface protocol; likewise SNMP Q-adapter translates between SNMP and CMIP.

11. TMN System Components • 4. Network Element (NE) In the scope of TMN, an NE contains manageable information that is monitored and controlled by an OS. In order to be managed within the scope TMN, an NE must have a standard interface. If an NE does not have a standard interface, the NE can still be managed via a Q-adapter. The NE provides the OS with a representation of its manageable functionality (i.e., the MIB). Note that the NE contains NE functionality – that is, the functions required in order to be managed by an OS. As a building block, the actual NE can also contain its own OS function, as well as QA function, MD function etc.

12. TMN System Components • 5. Work Station (WS) The WS performs workstation functions. WSs translate information between TMN format and a displayable format for the user. • 6. Data Communication Network (DCN) The DCN is the communication network within a TMN. The DCN represents OSI layers. The DCN is used in the management of all network elements in the central office including the voice networking components, SONET/SDH equipment and digital cross-connect systems.

13. TMN Interfaces