network management principles and practice mani subramanian 2nd edition ch10

This Book

Notes

Bookmarks

Search

Contents

NetworkManagement:Principles andPractice

Table of ContentsIndex

Copyright

Endorsements

Preface

About the Author

Pt. I. Background

Pt. II. SNMP and NetworkManagement

Pt. III. TMN and ApplicationsManagement

Ch. 10. TelecommunicationsManagement Network

Why TMN?Operations Systems

TMN Conceptual Model

TMN Standards

TMN Architecture

TMN ManagementService Architecture

TMN Integrated View

TMN Implementation

Summary

Exercises

Ch. 11. NetworkManagement Applications

Pt. IV. Broadband NetworkManagement

Appx. A. OSI Network andSystem Management

Appx. B. Project Suggestions

Appx. C. Laboratory Tutorial

Appx. D. Spread SpectrumTechnology: OFDM

Chapter 10. Telecommunications Management Network > Why TMN?

Related Content

10.1. Why TMN?With the proliferation of SNMP management that has left OSI networkmanagement by the wayside, we can ask the question why we are spendingtime on discussing TMN. Historically, TMN was born out of necessity toextend the private and proprietary, but well-developed networkmanagement systems, and make them interoperable. In those days, thelarge telecommunication organizations referred to the systems thatmaintained the network and network elements as operations systems. ITU-Tformed a working group in 1988 to develop a framework for TMN. ISO wasalso working on standardizing network management with OSI managementframework using CMIP. With globalization and deregulation of thetelecommunications industry, the urgency for interoperability of networkmanagement systems was strongly felt. With the slow progress of thesestandards bodies, industry-sponsored groups such as the NetworkManagement Forum started developing standards in parallel to speed up theprocess.

Unfortunately, the standards and frameworks developed were so complexand expensive to implement using the then-present technology, TMN andOSI network management never got off the ground. However, TMN is theonly framework that addressed not only management of network elements,but also the management of network, service, and business. These laterissues are so critical in today’s business environment with numerousnetwork and service providers (they are not the same as they used to be).Customer service, quality, and cost of business form a three-legged stool[Adams and Willetts, 1996]. You knock out one leg and the stool fallsdown. TMN framework not only addresses the management of quality ofnetwork and network elements, but also service management and businessmanagement.

Further, in today’s corporate environment, buyouts and mergers demandinteroperability and business management. With the work environmentgoing into cyberspace and the Internet facilitating global communicationstraversing multiple service providers’ networks, the exchange ofmanagement information has become all the more important. All thesemotivations have revived the interest in TMN architecture.

It is to be kept in mind that TMN had been developed based on OSImanagement principles. However, it could be implemented, as is now beingdone, using other management technology, such as the well establishedSNMP management as well as newer ones described in Chapter 16.Organizations such as TM Forum are devoting efforts to accomplish this.

Network Management: Principles and Practice > Review of Information ... file:///D:/TC Engg/8th Semester/TMN/Book Network Management Princ...

1 of 1 23-Sep-15 8:04 PM

This Book

Notes

Bookmarks

Search

Contents



Copyright

Endorsements

Preface

About the Author

Pt. I. Background




Why TMN?

Operations SystemsTMN Conceptual Model

TMN Standards

TMN Architecture


TMN Integrated View

TMN Implementation

Summary

Exercises







Trademarks

Acronyms

Glossary

References

Index

Chapter 10. Telecommunications Management Network > Operations Systems

10.2. Operations SystemsTMN is built using the building blocks of the operations support system. Theuse of the terminology, operations support system, in the telephone industrywas changed to operations system, as it is also used to control the networkand network elements. For example, user configurable parameters in theATM network can be controlled by users via the M3 interface, as we willlearn in Chapter 12. The operations system (let us not confuse operationssystem with operating system) does not directly play a role in theinformation transfer, but helps in the OAMP of network and informationsystems. Figure 10.1 and Figure 10.2 present two examples of operationssystems that are used in the operation of telephone network and services:trunk test system and traffic measurement system. The terminology of OSSis back in common use again. We will use both terms in this chapter.

Figure 10.1. Operations Support System for NetworkTransmission

[View full size image]

Figure 10.2. Operations Support System for Traffic Measurement

The trunk test system shown in Figure 10.1 is used to monitor the loss andsignal-to-noise ratio in the trunk transmission system in Bell System. Atrunk is a logical entity linking two switching offices. It can seize anyavailable cable facility between the switches while carrying traffic. In order


1 of 2 23-Sep-15 8:04 PM

Related Content

to ensure quality of service, loss and signal-to-noise on the trunks aremeasured at regular intervals by accessing every trunk at each switchingoffice. This is done from a centralized test center. Any trunk that fails tomeet the minimum criteria set for quality control is removed from service.Thus, by removing a trunk out of service as it is failing (but before it actuallyfails), the customer does not see any degradation of service. The same testsystem is also used for an on-demand test to track troubles.

Except during popular holidays such as Mother’s Day, telephone service isalmost always available for communication at any time of the day. This isdue to careful planning and implementation of adequate facilities for trafficto be handled without being blocked for lack of facilities. Figure 10.2 showsa traffic measurement operations system, which measures the busy statusof switch appearance (access point) on each switch. As the statistics on thenumber of paths being busy increases, either due to the lack of accesspoints or the lack of adequate trunk facilities, additional equipment is addedto reduce blocking.

The above two examples of operations systems illustrate the necessity ofthe role of operations systems in the OAMP of telecommunication network.They are part of the telecommunications network management activities,and fall under the performance management function of the networkmanagement that we have defined under the OSI model in Chapter 4.


2 of 2 23-Sep-15 8:04 PM

This Book

Notes

Bookmarks

Search

Contents



Copyright

Endorsements

Preface

About the Author

Pt. I. Background




Why TMN?

Operations Systems

TMN ConceptualModelTMN Standards

TMN Architecture


TMN Integrated View

TMN Implementation

Summary

Exercises







Trademarks

Acronyms

Glossary

References

Index

Chapter 10. Telecommunications Management Network > TMN Conceptual Model

10.3. TMN Conceptual ModelFrom a TMN point of view, the network management system is treated as anoperations support system, as shown in Figure 10.3. It manages the datacommunication and telecommunication network.

Figure 10.3. TMN Relationship to Data and TelecommunicationNetworks


We differentiated the data or computer communication network from thetelecommunication network in Chapter 1 (see Figure 1.4). Figure 10.3extends it to TMN, where operations support systems, including the networkmanagement system, form a support network. It is logically a separatenetwork, but may or may not be physically separate based onimplementation. The telecommunication network in Figure 10.3 consists ofnetwork elements of switching exchanges and transmission systems. It isprimarily the wide area network of communications. Switching systemsinclude both analog and digital switches. And so are the transmissionsystems of both analog and digital types and include all means of transportfacilities including twisted pair, coaxial, fiber optics, and wireless.

Data communication network components consist of LANs, bridges, routers,gateways, and hosts. The workstation shown in Figure 10.3 that isattached to the data communication network is a distinct element of TMN,whose interface we will discuss later.

The TMN in Figure 10.3 is a network in its own right, and not just themanagement of telecommunication network. (It is TMN and not TNM.) ITU-TRecommendation M.3010 defines TMN as a conceptually separate networkthat interfaces to one or more individual telecommunication networks atseveral points in order to send or receive information to or from them andcontrol their operation. It consists of a network of operations systemsincluding a network management system, which, as we stated earlier, is alsoconsidered an operations system.

Figure 10.4 shows the TMN conceptual model. Notice that in this model not


1 of 3 23-Sep-15 8:04 PM

only are the networks and operations system depicted, but also services andhuman resources are brought in. The two columns in the figure depict theidentical components of the two service providers, A and B.

Figure 10.4. TMN Conceptual Model

We identify the following components in Figure 10.4: workstations,operations systems, network, services, and interfaces. Of course, there arethe operators who operate on the systems and the customers who use theservices.

Customers are provided service by the service provider, and customerservice should play a key part in the service provider’s business. Thus,service management is an important consideration in conceptualizing theTMN model.

The service provided by the service provider to the customer istelecommunication service, which means that the telecommunicationnetwork needs to be operated efficiently and economically. The OAMP on thenetwork needs to be handled in as much of an automated mode as possibleto increase the response time and to decrease the cost. Cost considerationslead to business management, which is addressed by the TMN model.

Service management, business management, and network management areall accomplished either partially or totally using the operations systemsshown in Figure 10.4. System operators interface with the operationssystems using workstations.

The interfaces associated with various functions and services have beenstandardized in the TMN model. Notice the three interfaces—Q3, F, and X.Q3 is the interface between the operations system and the network element.F is the interface between the workstation and the operations system.Information exchange between operations systems within a TMN isaccomplished using the Q3 interface, whereas operations systems belonging


2 of 3 23-Sep-15 8:04 PM

Related Content

to different TMNs communicate over the X interface. We will discussinterfaces in more detail in Section 10.5.


3 of 3 23-Sep-15 8:04 PM

This Book

Notes

Bookmarks

Search

Contents



Copyright

Endorsements

Preface

About the Author

Pt. I. Background




Why TMN?

Operations Systems


TMN StandardsTMN Architecture


TMN Integrated View

TMN Implementation

Summary

Exercises







Trademarks

Acronyms

Glossary

References

Index

Chapter 10. Telecommunications Management Network > TMN Standards

10.4. TMN StandardsITU-T is the standards body that has developed TMN standards. It is basedon the OSI framework. Its scope has been expanded and a good review of ithas been published [Sidor, 1995]. The TMN recommendations and scopeare summarized in Figure 10.5 [NMF] and Table 10.1. M.3000 documentpresents a tutorial of TMN. The other documents in the M series addressTMN architecture, methodology, and terminology. The Q series addressesthe Q interface, such as Q3 and G.733, the protocol profile for the Qinterface. These are listed in Table 10.1. Table 10.2 lists some of thestudy groups that are responsible for various TMN activities.

Figure 10.5. TMN Recommendations and Scope


Table 10.1. TMN Documents

M.3000 Tutorial Introduction to TMN

M.3010 Principles for TMN

M.3020 TMN Interface Specifications Methodology

M.3100 Generic Network Information Model forTMN

M.3180 Catalogue of TMN Managed Objects

G.774 SDH Network Information Model for TMNPDH Network Information Model for TMN

M.3200 TMN Management Services IntroductionTMN Management Services 1

TMN Management Services n

M.3300 F-interface Management Capabilities


1 of 3 23-Sep-15 8:04 PM

M.3400 TMN Management Functions

Q.811Q.812

Protocols for the Q Interface

G.773 Protocol Profiles for the Q Interface

Table 10.2. ITU-T Study Groups

StudyGroup

Study Topic RecommendationSeries

SG 2 Traffic management M series

SG 4 TMN architecture definition Genericnetwork model F-interface

SG 7 OSI base management standardsData network management andMHS

Customer network management

X series

SG 10 User interfaces Specificationlanguages

SG 11 TMN protocols and profilesSwitching and signaling systemmanaged objects

ISDN management protocol andinformation models

Intelligent network management

UPT management

Q series

SG 13 B-ISDN requirements (transportnetworks) ISDN

SG 14 Modem management V series

SG 15 Transmission system managementTransmission system modeling

SDH, PDH, ATM management

G series

SG 18 Broadband managementrequirements

JRM (JCG) Overall coordination of TMN

The other supporting documents are also shown in Figure 10.5. Networktraffic management, maintenance, and security are covered in E and Mseries. The communication protocol, CMIP, and service elements, CommonManagement Information Service Element (CMISE), are covered in I and Xseries documents. A discussion of the X series is covered in Appendix A.Please refer to Appendix A of [NMF] for a complete list of the variousseries in Figure 10.5.

TMN standards define two types of telecommunication resources: managedand operations systems and the interfaces between them [Sidor, 1995,1998]. Architectural definitions of the communicating TMN entities, theirroles in TMN, and their interrelationship are described in M.3010. M.3020provides an overview. The common services of OAMP functions are definedin M.3200. The functions associated with individual TMN managementservices are described in M.3200 series. A generic set of TMN managementfunctions, based on OSI management functional areas, is specified in


2 of 3 23-Sep-15 8:04 PM

M.3400.

Management application messages and information models to support OAMPrequirements are specified in M.3100 series and G.774. A generic networkinformation model is defined in M.3100 that addresses common solutions forthe management of resources of the network such as switching,transmission, and other technologies. OSI management services and CMISare defined in X.710. TMN-related messages are contained in theinformation model defining application protocols and support objects, whichare covered in Q-series documents.

Communication protocols are addressed in the respective protocol-specificstandards documents. The G series addresses those that are not covered inthem, but are relevant to TMN, such as SDH network management (G.784).


3 of 3 23-Sep-15 8:04 PM

This Book

Notes

Bookmarks

Search

Contents



Copyright

Endorsements

Preface

About the Author

Pt. I. Background




Why TMN?

Operations Systems


TMN Standards

TMN ArchitectureTMN ManagementService Architecture

TMN Integrated View

TMN Implementation

Summary

Exercises







Trademarks

Acronyms

Glossary

References

Index

Chapter 10. Telecommunications Management Network > TMN Architecture

10.5. TMN ArchitectureTMN architecture is defined in M.3010 describing the principles for a TMN.There are three architectural perspectives: functional, physical, andinformation, as shown in Figure 10.6. The functional architecture identifiesfunctional modules or blocks in the TMN environment, including thereference point between them. The requirements for interface are specified.The physical architecture defines the physical blocks and interfaces betweenthem. Information architecture deals with the information exchangebetween managed objects and management systems, using a distributedobject-oriented approach. We will look at each of these three perspectives inthe next three subsections. You may also obtain more details from thereferences [Cohen, 1994; M.3010; NMF; Raman, 1999; Sidor, 1998].

Figure 10.6. TMN Architecture

10.5.1. Functional ArchitectureM.3010 defines TMN architecture made up of five function blocks: operationssystems function, network element function (NEF), mediation function (MF),workstation function (WSF), and Q-adapter function (QAF), as shown inFigure 10.7. Each function block contains a set of functions. There aremultiple instances of each function. Thus, for example, there may be manyoperations systems performing different operational functions in theoperations systems’ function block. The communication between thefunction blocks itself is a function, but not a function block, defined as theTMN data communication function (DCF). DCF supports the standardtransport protocols.

Figure 10.7. TMN Functional Architecture


1 of 5 23-Sep-15 8:03 PM

The TMN operations systems function (OSF) is implemented inoperations systems. As we saw in Section 10.2, operations systems (OS)such as network transmission OS and traffic measurement OS help monitor,manage, and control telecommunication networks and services. Networkmanagement, both as a manager and an agent, is also considered to be anOS. This would include MIB in Internet management and naming tree in OSImanagement as a function of the OSF.

The TMN NEF is concerned with the managed network elements. Networkelements themselves are not part of TMN, but are supported by TMN overthe standard interfaces. Network elements would include hardware,software, and systems such as hubs, routers, switches, processes, etc. Thenetwork management agent and the associated MIB are part of the NEF.Network elements providing information for management, such as packetsdropped, collision rate, etc., are considered as part of TMN, i.e., NEF.

The TMN MF block addresses the operations performed on the informationcontent passing between the network elements and operations systems.Such operations include filtering, store and forward, protocol conversion,threshold detection, etc. A physical entity in which the MF is implementedcan be shared between multiple operations systems and network elements.For example, a remote monitoring device (RMON) can monitor a remote LANon various parameters such as statistics on users, protocols, and packet lossand report the analyzed data or raw data to accounting and performancemanagement operations systems. In this situation, the RMON device acts asa mediation device performing MF between the network elements on theremote LAN and the operations systems (or network management systems).

The TMN WSF provides an interface between human personnel and TMNactivities. More specifically, this function addresses the presentation aspect.The conversion function that converts machine-readable information tohuman-interpretable format in the presentation function belongs in one ofthe other three function blocks, OSF, MF, and QAF (explained later). Thiswould cover the presentation function such as graphical user interface (GUI)and human–machine interface of workstations.

Communication between the above four functional blocks, OSF, WSF, MF,and NEF, is assumed to be standardized. Of course, this is far from thereality of the world. Therefore, in order to accommodate the legacyfunctionality as part of TMN, a TMN QAF has been defined. This is somewhatsimilar to a proxy server in SNMP management, where non-SNMP networkelements are managed by an SNMP manager via a proxy server. Thus, TMNnoncompliant devices are connected to a TMN-compliant system/network


2 of 5 23-Sep-15 8:03 PM

using a Q-adapter interface.

Each function in the function block can be considered as providing a serviceand the service block providing a set of services. An example would be asecurity management application function as either part of or a stand-aloneoperations system. As shown in Figure A.13 in Appendix A, there areseveral security system management functions such as alarm reporting,audit trail, etc. associated with the security functional area. In fact, all fivemanagement functional areas of configuration, fault, performance, security,and accounting residing in a network management system would belong toOSF.

Function blocks are designed to be nonoverlapping. However, this does notmean that different function blocks do not use some of the same functions.For example, the MIB is a function that is used by several function blocksthat enable them to exchange management information. Another examplewould be the scheduling function shown in Figure A.13. This could be usedby the performance management application to gather traffic statistics, bythe configuration system to discover and delete network elements, and bythe fault management system to gather errored-seconds on unstableelements.

Notice that the function blocks in Figure 10.7 are connected with interfacesdesignated by x, q3, qx, and f. These are called TMN service interfaces orsimply, TMN interfaces. The TMN interface between function blocks, shownin Figure 10.8, is called a TMN reference point. A reference point can beconsidered to be a conceptual point of information exchange betweenfunction blocks. An interface between a management agent embedded in anetwork element and a network management system will be a q3 referencepoint. When a network management system automatically creates a troubleticket in a trouble tracking system, it is communicating via an x-referencepoint. When a Web browser interfaces with a Web-based managementsystem, it is accessing an f-reference point. When a TMN-noncompliantswitch is managed by a TMN-compliant operations system using a Q-adapterinterface, it is interfacing via a qx interface.

Figure 10.8. TMN Reference Point

Summarizing, some examples of network devices implementing TMNfunctional components are operations systems, network managementsystem, application, network element, management network agent,management information base, RMON, proxy server, GUI, and Web browser.Remember again that DCF such as SNMP, CMIP, and common object requestbroker architecture (CORBA) is not included here.

The information exchange going across the TMN reference points can beclassified into three classes: q-class, f-class, and x-class. The q-classreference point interfaces to the management application function. InFigure 10.7, the q-class reference point includes both q3- and qx-classTMN reference points. An f-class TMN reference point is an interfacebetween the WSF block and any other function block in TMN. An x-class TMNreference point is an interface between two operations system function(OSF) blocks belonging to two different TMNs, as shown in Figure 10.7. Theinterface information pertains to functionality of similar nature.

TMN reference points are designated by lowercase letters, q, f, and x, whilethe associated interfaces in the physical embodiment are identified usinguppercase letters, Q, F, and X, as we shall see in the next section.


3 of 5 23-Sep-15 8:03 PM

10.5.2. Physical ArchitectureITU-T Recommendation M.3010 presents a model for the TMN physicalarchitecture, shown in Figure 10.9. A TMN physical block could be anembodiment of one or more blocks, besides its equivalent function block. Forexample, an operations system could have its operation function as well asmediation device, which does filtering of information. There are five types ofphysical blocks representing the five functions discussed in the previoussection, excluding the TMN DCF.

Figure 10.9. TMN Physical Architecture

Operations systems are embodiments of TMN OSF. It is connected to themediation device, placing the MF on a data communication network. Thedata communication network is the physical implementation of DCF, which torepeat, is not a function block, but a TMN function, DCF. The networkelements, Q adapter, and workstations reflect their respective TMNfunctions.

The Q, F, and X TMN interfaces between the physical devices are also shownin Figure 10.9, representing the physical implementation of the respectiveTMN reference points. The Q3 interface is used between the OS and eitheran NE or a QA. The Qx interface is shown between MD and QA/NE. Anexample of this would be an MD being a proxy server communicating withlegacy systems via the QA interface. The F interface is implemented toconnect a workstation to TMN. The X interface is between the operationssystems belonging to two different TMNs.

10.5.3. Information ArchitectureThe TMN information architecture initially adopted the OSI managementinformation architecture, CMIP/CMIS, defined in the ITU-T X.700 series anddiscussed in Appendix A. However, with the wide acceptance of InternetSNMP, extensively covered in our earlier chapters, deployment is in progressusing both models in TMN. We have covered both management models inthis book. The OSI information model is object oriented and the SNMPmodel is scalar. Both models are based on the dual roles that entities play ininformation exchange: manager and agent. Figure 10.10 shows the


4 of 5 23-Sep-15 8:03 PM

information exchange between the two types of entities. The managerperforms operations or makes requests from an agent. The agent executesthe operations on the network elements that it is managing and sendsresponses to the manager. The agent also sends unsolicited messages to themanager indicating alarm events.

Figure 10.10. TMN Information Architecture

Information models specified by SNMP and OSI management deal with themanagement of network elements. The TMN information model has beenused in specific technology such as ATM and SDH/SONET, which we willcover in Chapter 12.

The information architecture should transport information reliably across thefunctional boundaries. There are two types of communication servicesbetween interfaces: interactive and file oriented. We will discuss theinteractive service in Appendix A. It is supported in OSI by CMISE overRemote Operations Service Element (ROSE). In the Internet distributedcomputing environment (DCE), this will be handled by Remote ProcedureCall (RPC). The file-oriented category is supported by File Transfer AccessManagement (FTAM) in OSI [Raman, 1999] and in the Internet by FileTransfer Protocol (FTP). In the OSI model, Association Control ServicesElement (ACSE) is needed to establish, release, and abort applicationassociations. In the Internet model, this is integrated in RPC presentationservice. You may consult the reference [Piscitello and Chapin, 1993] formore details on this subject.


5 of 5 23-Sep-15 8:03 PM

This Book

Notes

Bookmarks

Search

Contents



Copyright

Endorsements

Preface

About the Author

Pt. I. Background




Why TMN?

Operations Systems


TMN Standards

TMN Architecture

TMN ManagementService ArchitectureTMN Integrated View

TMN Implementation

Summary

Exercises







Trademarks

Acronyms

Glossary

References

Index

Chapter 10. Telecommunications Managemen... > TMN Management Service Architecture

10.6. TMN Management Service ArchitectureAnother functional model of TMN is based on the services provided in a TMNenvironment. The TMN services are grouped and presented as TMN layeredarchitecture, as shown in Figure 10.11 [M.3400]. This layered architectureis not the same in the strict sense of protocol layered architecture, in thatcommunication can occur between nonadjacent layers.

Figure 10.11. TMN Service Architecture

The lowest layer is the network element layer comprising networkelements such as switches, routers, bridges, transmission facilities, etc. Thenext layer, the network element management layer, manages thenetwork elements. The third layer is the network management layer,which manages the network. The network management functions in thislayer would include bandwidth, performance, quality of service, end-to-endflow control, network congestion control, etc. The network element layerand the network element management layer are vendor dependent, whereasthe network management layer is not.

The service management layer is concerned with managing the servicesprovided by a network service provider to the customer or to anothernetwork service provider. This will include services such as billing, orderprocessing, complaints, trouble ticket handling, etc. The top layer in Figure10.11 is the business management layer. This is concerned withmanaging a communications business, such as fiscal considerations,personnel needs, project management, and customer needs andsatisfaction.

We notice that the TMN reference point between the various service layers isq3, which is the standard interface between operations system, network


1 of 2 23-Sep-15 8:03 PM

element, and MFs shown in Figure 10.7.

The TMN management services are classified into OSI system managementfunctional areas, which are the five OSI application functions described inSection 3.9. They are configuration management, fault management,performance management, security management, and accountingmanagement. This is presented in Figure 10.12.

Figure 10.12. TMN Management Services and ManagementFunctional Areas



2 of 2 23-Sep-15 8:03 PM

This Book

Notes

Bookmarks

Search

Contents



Copyright

Endorsements

Preface

About the Author

Pt. I. Background




Why TMN?

Operations Systems


TMN Standards

TMN Architecture


TMN Integrated ViewTMN Implementation

Summary

Exercises







Trademarks

Acronyms

Glossary

References

Index

Chapter 10. Telecommunications Management Network > TMN Integrated View

10.7. TMN Integrated ViewNow that we have discussed various aspects and perspectives of TMNarchitecture, let us look at the overall picture of how all these fit together. Arepresentation of this is shown in Figure 10.13.

Figure 10.13. TMN Services and Functions

The four TMN management services—business, service, network, andelement—are at the top of the hierarchy. They invoke the systemmanagement functions defined in the system management functional areas.The five components in the system functional areas are the managementapplication functions: configuration, fault, performance, security, andaccounting.

The management applications in the system functional areas perform eithersystem management functions or TMN functions. The TMN function blocks,OSF, WSF, NEF, MF, and QAF, constitute the TMN function blocks. The TMNfunction blocks are made up of TMN functional components such as networkmanagement function, MIB, etc. DCF, although not part of TMN functionblocks, is included for completeness.

System management functions include functions such as objectmanagement, alarm management, etc. System management functions arediscussed in Appendix A, Section A.6. In Figure 10.13, we could have


1 of 2 23-Sep-15 8:03 PM

Related Content

embedded the system management functions in TMN function blocks andTMN functional components, but have shown them separately in order tovisualize them in a non-OSI environment. TMN has been exclusivelyassociated with the OSI environment and it is only recently that it is beingconsidered in the popular SNMP environment.

System management functions and TMN functions invoke the primitiveservices. Figure 10.13 shows the OSI primitive services of M-GET, M-SET,etc. Equivalent SNMP services will be GET-REQUEST, SET-REQUEST, etc.

The TMN environment is a distributed environment. The applicationscommunicate remotely with the communication transport service using RPC.In the OSI model, RPC is accomplished with ROSE and ACSE. The formerdoes the remote operation, and the latter establishes and releases theapplication association. In the SNMP management model, the remoteoperation is accomplished using RPC and TCP/IP.


2 of 2 23-Sep-15 8:03 PM

Chapter 10. Telecommunications Management Network > TMN Implementation

Although the TMN concept was proposed in the early 1980s, it has notfound wide acceptance for several reasons [Glitho and Hayes, 1995;Raman, 1998]. Some of these are its strong dependency on exclusiveOSI network management, high resource requirement, technicalcomplexity, lack of complete standards, popularity and simplicity ofSNMP management, and implementation difficulties.

Industry and computer technology were not quite ready in the 1980s tofully implement (or even partially implement) the object-oriented OSInetwork management due to its complexity. The object-oriented andlayered OSI protocol stack demanded processor resources that werebeyond the capability of the technology then. However, present-dayhardware resources can handle such demands. OSI toolkits arecurrently available both commercially and as freeware. Using thesetools, products have been developed for trouble ticket administration(TMN X interface) and Integrated Digital Loop Carrier (TMN Q3interface) recently [Raman, 1999].

Object-oriented technology in those years, as for example DCE andCORBA, was not at the same level as it is today. This has revived thework on distributed management environment [Autrata and Strutt,1994] using the object-oriented approach.

Even with resources and toolkits available, one cannot avoid the legacysystems interfacing with TMN [Glitho and Hayes, 1996]. This isaccomplished using either the TMN Q adaptation (TMN QA) interface oradding a new Q (TMN Q3) interface. The choice between the two isbased on cost for each approach to accomplish OAMP of atelecommunications network.

There are three forums that have actively promoted the implementationof TMN: ATM Forum (now IP/MPLS Forum), NMF (formerly known asNetwork Management Forum), and recently TM Forum. We covered theATM Forum’s application for ATM in Chapter 9. We will now brieflyconsider NMF’s activities. TM Forum’s activities are addressed inSection 10.8.2 and in Chapter 16.


1 of 5 23-Sep-15 8:03 PM

An example of the realization of TMN architecture is presented in Figure10.14 [NMF]. The left side of the figure shows the TMN logical layeredarchitecture and the right side a physical realization of it. Each layerconsists of several management systems providing the various services.The layered architecture shows the TMN q3 reference points and thephysical realization the corresponding Q3 interfaces.

Figure 10.14. TMN Realization Example (NMF)

The Network Management Forum, later referred to as NMF, is anindustry-sponsored forum. NMF has developed a program calledOMNIPoint, which stands for Open Management Interoperability Point.The objective is to help companies implement management standardsacross a wide range of suppliers’ equipment. It has developeddocuments [NMF] that specify mapping between the Internet and OSIstandards that help TMN implementation in a hybrid managementenvironment.


2 of 5 23-Sep-15 8:03 PM

The TeleManagement Forum (TM Forum) is a body whose mission is toalign technology with real business, and thus is the next sequential stepin the process of TMN implementation. An important goal of the TMForum is to automate end-to-end the operations that enable delivery of“information, communication and entertainment services,” andEnhanced Telecom Operations (eTOM) is the framework to accomplishthis mission. eTOM is a framework specification and provides a businessprocess model to the telecommunications industry to define theprocesses end-to-end. Figure 10.15 depicts the business processarchitecture defined by eTOM.

Figure 10.15. eTOM Business Process Framework—Level 0processes


The business processes are described in a layered hierarchical fashion,where process at each level can be broken down into lower-levelprocess elements. eTOM is structured in three broad areas or Level 0processes—Strategy, Infrastructure, and Product (SIP); Operations(OPS); and Enterprise Management (EM). Of these areas, the OPS areasof service management and operations, and resource management andoperations come within the purview of network management and


3 of 5 23-Sep-15 8:03 PM

address a perspective similar to the functional model covered inSection 3.9. Each Level 0 process in turn contains detailed componentsat Level 1, 2, etc.

The ITU-T standard adopts the management service/function approach,while the eTOM framework adopts a business process approach thatbuilds on the management services/functions to develop a referenceframework that categorizes all business activities a service provider willuse. The main difference between the TMN and eTOM approaches is thatthe former has been developed starting from networks and networkequipment (bottom up) while eTOM is a top-down approach. The eTOMframework has been incorporated in toto within the TMN framework as aset of standards [M.3050.x].

Figure 10.16 depicts the subset of the layers of the eTOM map that areimplemented as applications in a typical NMS product alongside a roughcorrespondence with the more traditional ITU-T-based TMN visualization.While the management functional areas in TMN are referred to as FCAPS(fault, configuration, accounting, performance, and security), they arereferred to as FAB (fulfillment, assurance, billing) in eTOM.

Figure 10.16. eTOM-to-TMN Model


The applications in the box of Figure 10.16 are typically implementedas part of an NMS product. Figure 10.17 shows the Level 2 processesfor the Level 1 processes of FAB activities in service management andoperations, as well as resource management and operations. Each Level2 process element is in turn broken down into finer Level 3 elementsrepresenting a greater level of detail.


4 of 5 23-Sep-15 8:03 PM

Figure 10.17. eTOM Level 2 Processes-to-M.3400 Function SetGroups


The implementation of the OSI management application functionsdescribed in Section 3.9 is covered in detail by ITU-T specificationsM.3400. The mapping of these functions to Level 2 eTOM processes isshown in Figure 10.17. There is a one-to-one mapping of four of thefive functions, the exception being security management [M.3050 Sup3]. Figure 10.18 illustrates the mapping of the specific case ofconfiguration function mapped to eTOM Level processes.

Figure 10.18. eTOM Level 2 Processes-to-M.3400Configuration Function



5 of 5 23-Sep-15 8:03 PM

Chapter 10. Telecommunications Management Network > Summary

We have presented in this chapter a brief introduction to the complexsubject of Telecommunications Management Network (TMN). Although itwas proposed by ITU-T in the early 1980s, it is just now becoming areality due to the advancement of technology and the availability of OSIstandards and toolkits.

We learned the role of operations systems in operation, administration,maintenance, and provisioning (OAMP) as they are currentlyimplemented by telecommunication service providers. We defined theirrole in TMN. Network management system is considered an operationssystem in the TMN environment.

We defined the concept of TMN consisting of customers, servicesprovided by telecommunication service providers, network, operationssystems, and system operators. Due to the multitude of servicesprovided by a multitude of service providers using a multitude of vendorequipment, TMN has proposed reference points between the variouscomponents that define standard service interfaces. The original TMNproposal is exclusively OSI standards based.

TMN architecture is presented from three perspectives: functional,physical, and information. The functional architecture is made up of fivefunctions: operations system function (OSF), network element function(NEF), mediation function (MF), Q-adapter function (QAF), andworkstation function (WSF). The interface between them is defined bythree TMN reference points: f, q3/qx, and x.

TMN physical architecture is the physical manifestation of the functionalarchitecture with the functions implemented in operations systems,mediation devices, network elements, QAFs interfacing with non-TMNlegacy systems, and workstations. The data communication function is adistributed function carrying information between function blocks usingnetwork management operations, responses, and notifications.

TMN service architecture consists of four layers of management and afifth layer of network elements. The four layers of management areelement management, network management, service management, andbusiness management. We presented an integrated view of all thevarious components, showing how they all fit together to form the TMN


1 of 2 23-Sep-15 8:04 PM

environment. We discussed the issues and recent activities inimplementing TMN. We touched upon the recent advancement oftechnology and tools that have helped the implementation of TMN. Theroles played by the three forums–the ATM Forum, the NMF, and TMForum–were also addressed.


2 of 2 23-Sep-15 8:04 PM

Chapter 10. Telecommunications Management Network > Exercises

1. Shannon’s channel capacity theorem provides the followingrelationship for maximum channel capacity (bits per second)in terms of bandwidth B and signal-to-noise ratio S/N.C = B log2 (1+S/N)

The S/N in decibels (dB) is related to S/N in power ratio by

S/N in dB = 10(log10S/N)

The transmission operations system described in Figure10.1 monitors S/N of a telephone channel with a 3-kHzbandwidth and a channel capacity of 30 kbps. When S/Ndecreases by 3 dB, the operations system issues a warningalarm and the telephone trunk facility is taken out ofservice if S/N goes down by 6 dB. Calculate the channelcapacity in bps at (a) warning threshold and (b) out-of-service limit keeping the same 3-kHz bandwidth for thetelephone channel.

2. Design a traffic measurement operations system that monitorsthe packet traffic at layer-2 on the nodes shown in Figure10.2. Assume that all traffic is made up of unicast packetsand the links and nodes are such that the packets dropped atany node are primarily due to traffic overload on the node.The system measures the incoming and outgoing packetshandled by the data link layer as it interfaces with the physicaland network layers. Assume that the system permits the userto set the thresholds for action based on percent packet loss.

What MIB objects would you monitor?a.

Express the threshold parameters for congestion(percent packet loss) on the node as a function ofthe measured parameters.

b.

3. Figure 10.19 shows a network management environmentconsisting of a MoM (Manager of Managers) NMS, several


1 of 3 23-Sep-15 8:03 PM

agent NMSs that manage individual network domains, andmanaged network elements. Identify the TMN functionsperformed by:

MoM NMSa.

Agent NMSb.

Managed elementsc.

Figure 10.19. Exercise 3

4. A proxy server configuration (Figure 6.46) is used to manageSNMPv1 network elements by an SNMPv2 networkmanagement system.

What TMN function does a proxy server play in anNMS environment?

a.

Identify the interfaces of the proxy server to thenetwork manager and network elements.

b.

5. In Figure 10.19, identify all:

TMN reference pointsa.

TMN interfacesb.


2 of 3 23-Sep-15 8:03 PM

6. Associate M1 through M5 interfaces in ATM management(Figure 10.9 and Figure 10.10) with TMN reference pointsand TMN service interfaces.

7. CMISE services are listed in Table A.3. Map these services,wherever possible, to SNMPv1 services.

8. Repeat Exercise 7 comparing CMISE and SNMPv2 services.

9. TMN can be applied to ATM switch management using eitherSNMP or CMIP specifications. Research the ATM Forumspecifications referenced in Table 12.3 and identify theOBJECT IDENTIFIERS for the two modules,atmfM4CmipNEView and atmfM4Snmpview.

10. The ATM objects are defined under the nodeinformationModule(0), which is the subclass ofatmfCmipNEView. Five managed object classes are definedunder the informationModule, which are atmfM4ObjectClass,atmfM4Package, atmfM4Attribute, atmfM4NameBinding, andatmfM4Action. Draw a naming tree for these, explicitlyidentifying the ObjectID.

11. Figure 10.18 shows mapping of eTOM Level 2 processes-to-M.3400 Configuration Function. Do similar mapping ofeTOM Level 2 processes-to-M.3400 specifications for:

Fault Managementa.

Performace Managementb.

Accounting Managementc.


3 of 3 23-Sep-15 8:03 PM

network management principles and practice mani subramanian 2nd edition ch10

Documents

tmn andosi network management

service management

management of network

business management

tmn framework

management technology

establishedsnmp management

osi networkmanagement