Telecommunications Management Network (TMN)

1. Telecommunications Management Network(TMN) Ju Hong Taek College of Information and Communication Keimyung University Tel: 053-580-5234 Email: juht@kmu.ac.kr

2. Table of Contents • Introduction • TMN Principles • TMN Architectures • TMN Management Functions • Summary

3. Introduction • What is TMN? • The Role of the Management Platform • Trends in Telecommunications • Surviving the Evolving Telecom World • Designing a Management Platform • Why TMN?

4. What is TMN? • Telecommunications Management Network (TMN) • TMN project started fall 1985 • Initial recommendation CCITT M.30 (published in 1988) included work of several Study Groups • Renamed to recommendation M.3010 in 1992 which defines basic principles for TMN • The objective for the TMN specifications is to provide a framework for telecommunications network and service management

5. The Role of the Management Platform • Investment in telecommunication networks normally cover at least 5 years, the same applies to the management platform (ROI) • Investment in platforms for telecommunication network management forms a small part of the total investment • For many operations, operational costs for network and service management are higher than equipment costs • Changing service and equipment needs within operational platforms are common practice (competition). => Management platforms must be flexible to cope with changing environments. The platform plays a crucial role in competitive markets.

6. Trends in Telecommunications • Globalizations and Deregulation • End-to-end service (one stop shopping) involves multiple providers • Demand for standards based network and service management (interoperability) • Competition • Time-to market for new services • Need for sound (flexible) architecture • Focus on customer care (service quality) • Decreasing margins (do more with less) • Increase revenue (providing high quality services) while minimizing network operation costs

7. Trends in Telecommunications (2) • Service providers concentrate on core business and become part of value chain • Need for interworking to provide end-to-end management • Demand for standards based network and service management (interoperability) • Evolution in protocols (e.g., IP QoS issues, IP over WDM) • Impacts the value chain for service delivery • Need for flexible management architecture • Gradual merge of telecom and datacom world, e.g., datacom suppliers entering traditional telecom markets • Datacom management concepts are introduced in the telecom area (e.g., more autonomous networks) • Interworking between management protocols

8. Surviving the Evolving Telecom World • Be pro-active instead of re-active • Decrease service restoration time • Decrease provisioning time • Focus on customer care, including service flexibility (maintaining existing customers is more cost effective than attracting new customers) • Concentrate on cost for network operations • Forecasting of customer needs • Rapid deployment of new services • Flexibility towards equipment suppliers • People management

9. Service Processes Management Platform Network Designing a Management Platform • What functions are automated and what is implemented by processes? • What information must be maintained in the management platform? • How are functions and information mapped on the physical building blocks in the management platform?

10. Why TMN? The TMN Framework: • ensures interoperability • ensures scalability • is mature (large amount of telecom standards in GDMO) • provides security To survive in a highly innovative and competitive telecommunications market, use of a robust architecture for network and service management is a must.

11. TMN Principles • TMN Recommendations from ITU-T • Objectives • Relationship of a TMN to a Telecom Network • TMN Functional Architecture • TMN Information Architecture • CMIP/CMIS • TMN Physical Architecture • Logical Layered Architecture

12. TMN Recommendations from ITU-T

13. Objectives • 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” • The basic concept behind a TMN is to provide a 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 architecturewith standardized interfaces including protocols and messages

14. TMN OS OS OS To other TMN WS DCN EX EX EX TR TR Telecommunications Network Relationships between Telecommunication Network and TMN EX: Exchange TR: Transmission DCN: Data Communication Network OS: Operations System WS: Work Station

15. TMN Functional Architecture • The TMN functional architecture explains the distribution of functionality within a TMN • Distinction must be made between: • Role that a function performs (controlling, mediator role, management user oriented, information transport) • Actual function that is performed (configuration management, fault management, etc.) • Recommendation M.3010 concentrates on roles whereas M.3400 deals with functions

16. TMN Functional Architecture (2) 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.

17. TMN Functional Architecture (3) • Function blocks defined within M.3010: • OSF Operation Systems Function • MF Mediation Function • WSF Work Station Function • NEF Network Element Function • QAF Q Adaptor Function

18. TMN Functional Architecture (4) • Reference points defined within M.3010 (g and m are located outside the TMN): • q class between OSF, QAF, MF and NEF • f class for attachment of a WSF • x class between OSFs of two TMNs or between TMN OSF and OSF-like function in other network • g class between WSF and users • m class between QAF and non-TMN managed entities

19. g g WSF WSF TMN TMN f f f q3 x f q3 OSF OSF q3 q3 qx qx MF MF q3 q3 q3 qx q3 qx qx qx NEF QAF QAF NEF m m reference points TMN Functional Architecture (5)

20. TMN Information Architecture • In order to allow effective definition of managed resources, 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)

21. TMN Information Architecture (2) A managed object (MO) is defined by: • the attributes visible at its boundary • the management operations which may be applied to it • The behavior exhibited by it in response to management operations or in reaction to other types of stimuli (e.g., threshold crossing) • The notifications emitted by it

22. TMN Information Architecture (3) • Because the environment being managed is distributed, network management is a distributed application which requires exchange of information. • For a specific management association, the management processes will take one of two possible roles: • Manager, which issues operation directives and receives notifications • Agent, responds to directives and emits notifications (deals with the MO’s)

23. TMN Information Architecture (4) Agent Manager management operations M C F M C F R R application functions Q I/F R notifications TMN MCF: Message Communication Function R: Network Resource to be managed

24. TMN Information Architecture (5) Information Model B Information Model c system A system B system C MIB MIB sees sees M A M A CMIS CMIS CMIS CMIS CMIP Resource CMIP Resource Resource Resource OSI protocol stack OSI protocol stack * CMIP: Common Management Information Protocol * MIB: Management Information Base * CMIS: Common Management Information System

25. Management Processes CMIS CMIP ACSE ROSE CMIP/CMIS • CMIS (Common Management Information Services, X.710) is a service based on simple request/response approach • Operation services (M_CREATE, M_GET, M_SET, M_DELETE, M_CANCEL_GETM, M_ACTION) • Notification service (M_EVENT_REPORT) • CMIP (Common Management Information Protocol, X.711) defined the protocol to provide these services

26. CMIP/CMIS (2) • Scoping & Filtering • allows selection of multiple object instances to be operate upon by a single CMISE primitive • scoping identifies object instances to which a filter may be applied • filtering allows scoped object instances to be selected according to specific criteria • Synchronization • applies to operations on multiple instances • atomic (all or nothing) • best effort (anything goes) • Linked replies • permits multiple responses to a single operator request • applicable when scoping/filtering is used

27. TMN OS Q3/X/F G F X DCN WS Q3/F MD Q3 Q3 Qx DCN Qx Qx QA NE QA NE Interface M TMN Physical Architecture OS: Operations Systems MD: Mediation Device QA: Q-Adapter NE: Network Elements DCN: Data Communications Network WS: Work Station

28. BML SML NML EML NEL Logical Layered Architecture • Business Management Layer • Service Management Layer • Network Management Layer • Element Management Layer • Network Element Layer

29. Logical Layered Architecture (2) • The element management layer (EML) manages each network element on an individual basis and supports an abstraction of the functions provided by the NE layer. • Each element manager has the following principle roles: • control and coordination of a subset of network elements • provide a gateway function to permit the network management layer to interact with network elements • maintaining statistical, log and other data about elements • OSFs in the element layer always interface with OSFs in the network management layer through the q3 reference point

30. Logical Layered Architecture (3) • The network management layer (NML) has the responsibility for the management of all the NE’s, as presented by the EML, both individually and as a set. • The NML has the following principle roles: • control and coordination of the network view of network elements within its scope or domain • the provision, cessation or modification of network capabilities for the support of service to customers • interact with the service management layer on performance, usage, availability, etc. • OSFs in the NML always interface with OSFs in the service management layer through the q3 reference point

31. Logical Layered Architecture (4) • Service management layer (SML)is concerned with, and responsible for, the contractual aspects of services that are being provided to customers or available to potential new customers. • Principle roles for the SML: • customers facing and interfacing with other administrations • interaction with service providers • interaction with the SML • maintaining statistical data (e.g., QoS) • interaction with the business management layer • interaction between services

32. Logical Layered Architecture (5) • The business management layer (BML) 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) • The BML: • interacts with the service management layer • Is influenced by high levels of control such as legislation or macro-economic factors (e.g., tariffing policies, quality maintenance strategies)

33. TMN Management Functions • Fault management • Configuration management • Accounting management • Performance management • Security management FCAPS!

34. Summary • TMN strengths • TMN weaknesses Read www.simpleweb.org/tutorials/tmn/tmn.pdf

35. TMN Strengths • TMN is a very suitable framework for telecommunications management purpose since: • It identifies different abstraction levels • It forces a structure approach when faces with the problem of network and service management • It is a widely adopted standard, which ensures that everyone speaks the same language • TMN is particularly strong at the bottom layers of the TMN pyramid, using the power of OSI systems management and the associated object approach

36. TMN Strengths (2) • High interoperability by standardizing • protocol • information model • services • MIBs • scalability by well-developed reliable “event channel” (notifications with EFD discriminators) • complex types (structures) • scoping and filtering (OSI modeling) • TMN offers security, which is essential at EML and X interface

37. TMN weaknesses • Implementation of TMN isn’t so easy • TMN Q3 interface is based on a full OSI stack (solutions for stacks with reduced functionality are developed, e.g., CMIP on TCP/IP) • GDMO and ASN.1 are very complex (solution is the use of tools that hide GDMO and ASN.1). ASN.1 is designed for completeness, not simplicity. • TMN functional architecture does not map very well to service management. It originates from the bottom layers of the pyramid