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

2. 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

3. Trends In Telecommunications r Globalizations and Deregulation m End-to-end service involves multiple providers Demand for standards based network and service management (interoperability) r Merge of telecom and datacom m Need for Inter-working between management protocols to provide end-to-end management  Evolution in protocols o Need for flexible management architecture r Competition m Time-to market for new services Need for sound (flexible) architecture m Focus on customer care (i.e., service quality) m Decreasing margins (do more with less) Increase revenue (providing high quality services) while minimizing network operation costs

4. Example of Management (1) Trunk Testing System r Trunk is a logical connection between two switching nodes r Periodic measurement of loss and S/N of all trunks r Failing threshold set for QoS; failing trunks removed out of service before the customer complains

5. Example of Management (2) Telephone Switch Traffic r Traffic monitored at switch appearance r Call blocking statistics obtained r Traffic and call-blocking statistics provide data for planning r Importance of Operations, administration, mainte- nance, and provisioning

6. TMN Conceptual Model r TMN is conceptually a separate network r Interfaces between the TMN and the Telecommunication network are formed by exchanges and transmission switches r OSs (Operations Systems) perform most of the management functions and they are connected to TMN through a Data Communication Network (DCN) r The DCN is used to exchange management information between OSs

7. 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”

8. 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 r Information Architecture  Describes concepts that have been adopted from OSI management r Logical Layer Architecture  A model that shows how management can be structured according to different responsibilities

9. 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

10. TMN Functional Architecture  Interfaces between function blocks are defined as reference points qclass between OSF, QAF, MF and NEF fclass for attachment of a WSF xclass between OSFs of two TMNs or between TMN OSF and OSF-like function in other network gclass between WSF and users mclass between QAF and non-TMN managed entities

11. 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 users o They include management functions (i.e., agents)  Operation Systems Functions, OSF: o Operations and Notifications o Within a TMN, multiple OSFs may exist and they communicate through q3 interface o OSFs belonging to different administrative domains may also communicate through x reference point CMIP CMIS

12. TMN Functional Architecture  Work Station Function, WSF o Interprets management information to a human user through g interface  Q Adapter Function, QAF o Non TMN entities (e.g. proprietary) can be connected to a TMN entity o Translate between q reference point and m reference point (similar to a proxy agent in SNMP)

13. TMN Functional Architecture  Mediation Function (MF) o Located within the TMN o 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

14. TMN Functional Architecture  Data Communication Function (DCF) o Provide the necessary physical connection with various network components o DCF implements layers 1-3 of OSI o Connect NEs, QAs, and MDs to the OSs at the standard q interface o Connect MDs to NEs and QAs using q interface

15. TMN Physical Architecture

16. 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 boundary o the management operations which may be applied to it o 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

17. TMN Information Architecture MCFMCF MCFMCF R R R Agent management operations notifications Q I/F application functions TMN MCF: Message Communication Function R: Network Resource to be managed Manager Information Model based on Object-Oriented Approach MIT: dynamic structure, unlike MIB which is static

18. OSI System Architecture OSI Manager Application M-GET M SET 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- ment Data M ACTION M-EVENT-REPORT M-CREATEM-DELETE M-CANCEL-GET DLC OSI Agent Application M-GET M SET 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 ACTION M-EVENT-REPORT M-CREATEM-DELETE M-CANCEL-GET DLC

19. OSI System Architecture Managing Process Agent Process CMISE CMIP CMISE lower layers Management Function

20. OSI Information Model r A managed object (MO) is defined in terms of: m attributes it possesses m operations that may be performed upon it m notifications that it may issue m its relationships with other MOs r A managed-object class is a model or template for MO instances that share the same attributes, notifications, operations and behavior r A MO class can be created from other MO classes (called packages) Managed Object Class Conditional Package Attributes Behavior Operations Notifications Mandatory Package Attributes Behavior Operations Notifications Conditional Package Attributes Behavior Operations Notifications  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

21. OSI Information Model Hub Managed Object Class hub id vendor name model number serial number number of interfaces type of interfaces speed of interfaces Hub1 Instance hub id = “Hub1” vendor name = “ABC” model number =“abc” serial number = “123” number of interfaces = 12 type of interfaces = 6 speed of interfaces = 10000000 Hub2 Instance hub id = “Hub2” vendor name = “XYZ” model number =“xyz” serial number = “456” number of interfaces = 12 type of interfaces = 6 speed of interfaces = 10000000 Managed Object Class and Instances

22. OSI Information Model Switched hub Routershub Regular hub Switched 100-Mbps Hub Top Switched 10-Mbps Hub 10-Mbps Regular Hub Switched Multirate Hub 10-Mbps Uni-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 allmorphic o A subclass derived from multiple superclasses takes the properties of one superclass

23. 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 nameSpecifies a superclass Mandatory 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

24. OSI vs. SNMP OSI Mgmt (CMIP)Internet Mgmt (SNMP) Information Model Object-Oriented Scalar MIB Language GDMOSNMP SMI Mgmt Entity Interactions Manager-Agent, Manager-Manager Manager-Agent, Manager-Manager Protocol Operations M-Get, M-Set, M-Action M-Create, M-Delete M-Event-Report Get, Set limited Create/Delete Trap MO Addressing MIT with OID Scoping/Filtering MIT with OID at leaves of the tree Management Applications Five Functional Areas Not Specified Standardization Body ITU-T, ISOIETF Features

25. Management Service Architecture Vendor dependent

26. Management Service Architecture  Network Element Layer, NEL o Comprise NEs such as switches, routers, transmission facilities o Managed by the OSFs residing in the element management layer  Element Management Layer, EML oIt deals with vendor specific management functions and hide these functions from the layer above oFunctions performed: oDetection of equipment errors oMeasuring power consumption and the temperature of equipment oMeasuring resource usage: CPU, shared buffer, queue length, etc. oLogging of statistical data oEtc.. oNOTE: OSF in the element management layer and NEF may be implemented in the same piece of equipment

27. Management Service Architecture  Network Management Layer, NML oManaged functions related to interaction between multiple pieces of equipment (i.e., managing a network) oInternal structure of network elements is not visible (they are vendor specific) oFunctions performed: oCreate the complete network view oSetup/provisioning dedicated paths (with QoS parameters) for end users through the network oModifying routing table oMonitoring link utilization oOptimizing performance oFault detection oThe OSFs in NML interacts with the OSFs at the EML: it uses information provided by the EML to implement its functions oHere OSFs in NML acts as a manager and OSFs at EML acts as an agent

28. Management Service Architecture  Service Management Layer, SML oManage services provided by the network and seen by users oUsers may be end users (customers) and/or service providers using the telecommunication network oRelies on management information provided by the Network Management Layer (NML) oThe internal structure of the network (i.e., network details) are hidden oFunctions performed: oQoS management (delay, jitter, etc) oAccounting/billing oAddition/removal of users, etc.. oExample: inter-operator management oTwo 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).

29. Management Service Architecture  Service Management Layer, Example o A transport network (e.g., ATM, SONET or WDM) that is used by service providers to connect end routers and provide services Border OXC Core OXC IP Border Router UNI Client/Server Model

30. Management Service Architecture  Two independent control planes isolated from each other oThe IP routing, topology distribution, and signaling protocols are independent of the ones at the Optical Layer  Routers are clients of optical domain oThe 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

31. Management Service Architecture

32.  Example IP over ATM example oIP service provider connects to the ATM provider through X- reference points oThe details of the ATM backbone are hidden from the IP service provider oIP 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! oAn ATM link is considered as a single element for the IP network, therefore the reference point at the EML of IP oAnother reference point at the IP NML: oAllows for fault detection, rerouting, load balancing, optimization, etc.. oFinally, the IP network should monitor the ATM links for any degradation in network performance that may impact the QoS of the IP provider: oTherefore another reference point at the service management layer

33. Management Service Architecture  Business Management Layer, BML o 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 layer o Is influenced by high levels of control such as legislation or macro-economic factors (e.g., tariffing policies, quality maintenance strategies)