Skip to main content
Log in

An introduction to TMN

  • Papers
  • Published:
Journal of Network and Systems Management Aims and scope Submit manuscript

Abstract

The “Telecommunication Management Network” standard (ITU-T M.3010), the Network Magagement Forum “OMNIPoint” program, and many related developments are summarized. TMN and OMNIPoint are presented as a means to achieve integrated network management in the telecommunications industry by calling for all management systems to include an interoperable interface which permits each system to be integrated into a larger management hierarchy. By means of such interfaces, hierarchical integration of management systems can be achieved within the administration of a single service provider. Interoperable interfaces also make possible the interconnection of multiple service providers and the connection of customer to service provider, resulting in the possibility of industry wide integration of management infrastructures at all levels.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  1. All document designations referenced in this paper having the format of a single letter and a number separated by a dot are recommendations of the International Telecommunication Union-Telecommunication Standardization Sector (ITU-T), formerly the CCITT. Equivalent designations of the International Standards Organization (ISO) for those ITU-T recommendations which have been adopted as international standards are beyond the scope of this paper.

  2. ITU-T,Management Framework for Open Systems Interconnection, Recommendation X.700, 1993.

  3. ITU-T,TMN Management Functions, Recommendation M.3400, 1993.

  4. ITU-T,Principles for a Telecommunications Management Network, Recommendation M.3010, 1993.

  5. ITU-T,Management Framework for Open Systems Interconnection (OSI) for CCITT Applications, Recommendation X.700, 1993.

  6. ITU-T,Information Technology—Open Systems Interconnection—Systems Management Overview, Recommendation X.701, 1992.

  7. ITU-T,Common Management Information Service Definition for CCITT Applications, Recommendation X.710, 1991.

  8. ITU-T,Common Management Information Protocol Specification for CCITT Applications, Recommendation X.711, 1991.

  9. ITU-T,Service Definition for the Association Control Service Element, Recommendation X.217, 1993.

  10. ITU-T,Connection-oriented Protocol Specification for the Association Control Service Element, Recommendation X.227, 1993.

  11. ITU-T,Remote operations: Model, Notation and Service Definition, Recommendation X.219, 1989.

  12. ITU-T,Remote operations: Protocol Specification, Recommendation X.219, 1989.

  13. ITU-T,Reference Model of Open Systems Interconnection for CCITT Applications, Recommendation X. 200, 1989.

  14. ITU-T, Reference Model for Open Distributed Processing, Draft Recommendation X. 901, 1993.

  15. ITU-T, Basic Reference Model for Open Distributed Processing—Part 2: Descriptive Model, Draft Recommendation X. 902, undated.

  16. ITU-T, Basic Reference Model for Open Distributed Processing—Part 3: Prescriptive Model, Draft Recommendation X. 903, 1994.

  17. ITU-T, Basic Reference Model for Open Distributed Processing—Part 4: Architectural Semantics, Draft Recommendation X. 904, undated.

  18. ITU-T,Generic Network Information Model, Recommendation M. 3100, 1993.

  19. ITU-T,Information Technology—Open Systems Interconnection—Structure of Management Information: Management Information Model, Recommendation X. 720, 1992.

  20. ITU-T,Information Technology—Open Systems Interconnection—Structure of Management Information: Definition of Management Information, Recommendation X. 721, 1992.

  21. ITU-T,Information Technology—Open Systems Interconnection—Structure of Management Information: Guidelines for the Definition of Managed Objects, Recommendation X. 722, 1992.

  22. ITU-T,Specification of Abstract Syntax Notation One (ASN. 1), Recommendation X. 208, 1989.

  23. ITU-T,TMN Management Capabilities Presented at the F Interface, Recommendation M. 3300, 1992.

  24. ITU-T,Introduction to the CCITT Man-Machine Language, Recommendation Z. 301, 1989.

  25. ANSI,Operations, Administration, Maintenance, and Provisioning (OAM&P)—Extensions to Generic Network Model for Interfaces between Operations Systems across Jurisdictional Boundaries to Support Fault Management (Trouble Administration), T1. 227, 1992.

  26. ANSI,Operations, Administration, Maintenance, and Provisioning (OAM&P)—Services for Interfaces between Operations Systems across Jurisdictional Boundaries to Support Fault Management (Trouble Administration), T1. 228, 1992.

  27. The Electronic Communications Implementation Committee (ECIC) is a committee of the Telecommunications Industry Forum (TCIF) of the Alliance for Telecommunications Industry Solutions (ATIS).

  28. S. Allamagny, S. Civanlar, and A. N. Kashper, Capacity Management in Global Networking Project, inIEEE Network Oper. and Mgmt. Symp., Vol. 2, pp. 530–543, 1994.

  29. S. Allamagny, S. Civanlar, and A. N. Kashper Information Model for Capacity Management in Global Telecommunications Networks,JNSM, Vol. 2, No. 1, pp. 29–48, March 1994.

    Google Scholar 

  30. NMF,Discovering OMNIPoint: A Common Approach to the Integrated Management of Networked Information Systems, PTR Prentice Hall, 1993.

  31. NMF,ISO/CCITT and Internet Management: Coexistence and Interworking Strategies, Forum TR107, Issue 1.0, September, 1992.

  32. Copies of [31] and the other ISO/Internet Management Coexistence (IIMC) specifications can be obtained by FTP from nmf.org:/iimc/issue1.

  33. Marshall T. Rose and Dwight E. Cass, ISO Transport Service on top of the TCP, Version: 3, No. RFC 1006, Northrop Research and Technology Center, May 1987.

  34. CMOT (CMISE on TCP/IP) is a protocol which takes advantage of the fact that CMISE makes minimal use of the services of layers 4–6 and can be made to ride directly on X. 25 or TCP/IP. CMOT is not embraced by OMNIPoint because it defeats interoperability.

  35. NMF specification documents are generally available to NMF members only. Exceptions are documents such as the IIMC specifications [31], where the participation of the Internet community is required, some object libraries, and ensembles, which are made available for general use by the organizations contributing them. Technical documents available to non-members are generally available on the NMF BBS [47].

  36. NMF,Application Services: Testing Management Function, Forum 012, Issue 1.1, August 1992.

  37. NMF,Application Services: Scheduling Management Function, Forum 013, Issue 1.1, August 1992.

  38. NMF,Application Services: Path Tracing Management Function, Forum 014, Issue 1.0, August 1992.

  39. NMF,Application Services: Trouble Management Function, Forum 024, Issue 1.0, August 1992.

  40. NMF,Application Services: Security of Management, Forum 016, Issue 1.0, August 1992.

  41. NMF,Shared Management Knowledge Requirements, Forum 016, Issue 1.0, August 1992.

  42. NMF,OMNIPointI Managed Object Naming Specification, Forum 021, Issue 1.0, August 1992.

  43. NMF,Reconfigurable Circuit Service: Alarm Surveillance Ensemble, Issue 1.0, 1992.

  44. NMF,Reconfigurable Circuit Service: Configuration Ensemble, Issue 1.0, 1992.

  45. INTAP Network Management Technical Committee Ensemble Team, LAN Fault Management Ensemble, Draft 1, January, 1994.

  46. T. Choi and A. Tang,Enterprise Network Management: LAN Status Monitoring Ensemble, ver. 1.0, OSE Laboratory, Com. Sci. and Telecom. Prog., UMKC, 1994. Available by FTP from moon.ose.umkc.edu:/pub/doc.

  47. The RCS ensembles and GDMOs for a number of managed objects can be found on the NMF BBS, available by anonymous FTP from on nmf.org:/objects.

  48. The Newbridge “Connect Exec” product, which provides a CMISE interface for the “Main Street” element manager, is a result of this effort. The combination of these two products represents the first commercially available element manager which can be integrated into a larger TMN management hierarchy via on OMNIPoint interface.

  49. Bellcore,Generic Requirements For Element Management Layer (EML Functionality and Architecture), TA-TSV-001294, 1992.

  50. NMF,OMNIPointI Conformance Requirements, Forum 020, Issue 1.0, August 1992.

  51. NMF,OMNIPointI Testing Requirements, Forum TR108, Issue 1.0, August 1992.

  52. X/Open,X/Open Preliminary Specification, Systems Management: Management Protocols API (XMP), X/Open P170, 1992.

  53. X/Open,X/Open CAE Specification, OSI-Abstract-Data Manipulation API (XOM), X/Open C180, 1992.

  54. Object Management Group,The Common Object Request Broker: Architecture and Specification, OMG 91.12.1, 1991.

  55. X/Open,X/Open Systems and Branded Products: XPG4, X/Open X924, July 1992.

  56. Joint X/Open NMF Inter-Domain Management Task Force (JIDM), Translation of GDMO/ASN. 1 Specification into CORBA-IDL, Draft 0.02a, July 1994.

  57. NMF,Service Providers Integrated Requirements for Information Technology, Issue 1.0, September 1993.

  58. Personal Communications.

  59. CDPD Forum,CDPD System Specification, Release 1.1, 1994. This document can be purchased directly from CDPD Forum, Inc., at (800) 335–2373.

  60. OMNIPoint is a registered trademark of the Network Management Forum. The introductory documents reviewed here are available to non-members for purchase from Network Management Forum, 1201 Mt. Kemble Avenue, Morristown, New Jersey, 07960-6628.

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Shrewsbury, J.K. An introduction to TMN. J Netw Syst Manage 3, 13–38 (1995). https://doi.org/10.1007/BF02139832

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF02139832

Key Words

Navigation