1、ETSI TECHNICAL REPORT ETR 037 February 1992 Source: ETSI TC-NA UDC: 621.395 Key words: Network, TMN Reference: DTR/NA-43202 Network Aspects (NA); Telecommunications Management Network (TMN) Objectives, principles, concepts and reference configurations ETSI European Telecommunications Standards Insti
2、tute ETSI Secretariat: B.P.152 . F - 06561 Valbonne Cedex . France TP. + 33 92 94 42 O0 TF. + 33 93 65 47 16 Tx. 47 O0 40 F 0 European Telecommunications Standards Institute 1 992. All rights reserved. No part may be reproduced or used except as authorised by contract or other written permission. Th
3、e copyright and the foregoing restriction on reproduction and use extend to all media in which the information may be embodied. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Servicesm 3404583 0067382 2T3 m Page 2 ETR 037:1992 Whilst every care has been tak
4、en in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to “ETSI Standards Management Dept.“ at the address shown on the title page. COPYRIGHT European Telecommunications Standards In
5、stituteLicensed by Information Handling Servicesm 3404583 0067383 L3T m Page 3 ETR 037:1992 Contents Foreword . 7 Introduction 9 1 Scope . 10 1.1 Field of application 10 1.2 Basic objectives for the TMN . 12 1.3 Functions associated with a TMN 12 1.4 Architectural requirements . 13 2 The TMN functio
6、nal architecture . 14 2.1 Function blocks 15 2.1.1 Operations Systems Function block (OSF) 15 2.1.2 Network Element Function block (NEF) 16 2.1.3 Workstation Function block (WSF) . 16 2.1.4 Mediation Function block (MF) 16 2.1.5 Q Adaptor Function block (QAF) . 16 2.2 Functional components . 17 2.2.
7、1 Management Application Function (MAF) 17 2.2.2 Management Information Base (MIB) 17 2.2.3 Information Conversion Function (ICF) . 17 2.2.4 Human Machine Adaptation (HMA) . 18 2.2.5 Presentation Function (PF) . 18 2.2.6 Mediation Function . Management Application Function (MF-MAF) . 18 2.2.7 Higher
8、 Layer Protocol Interworking (HLPI) 18 2.3.1 Classes of reference points 18 2.3.2 Definitions of reference points 19 2.3.2.1 The q reference points . 19 2.3.2.2 The f reference points . 19 2.3.2.3 The x reference points 19 2.3.2.4 The g reference points . 19 2.3.2.5 The m reference points 20 . 2.3.2
9、.6 Relationship of reference points to function blocks . 20 2.4 Communications Functions of the TMN 20 2.4.1 Data Communication Function (DCF) 20 2.4.2 Message Communication Function (MCF) 21 2.5 The TMN reference model . 21 2.6 TMN access from external sources . 26 2.6.1 Access between TMNs . 27 2.
10、6.2 Access by network users . 27 2.6.3 Supporting external access to TMN functions . 27 2.3 TMN Reference points 18 3 The TMN information architecture 27 3.1 Object oriented approach . 28 3.2 Manager/agent . 29 3.2.1 Manager/agent/objects relationships . 30 3.2.2 Interworking between TMN function bl
11、ocks 31 3.3 Shared management knowledge . 31 3.3.1 Context negotiation . 33 COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesW 34U4583 00b7384 O76 W Page 4 ETR 037:1992 3.3.1.1 Static context negotiation 33 3.3.1.2 Dynamic context negotiation 33 3.4 D
12、omains . 34 3.4.1 Relationships between domains . 34 34 3.5 Logical layered architecture 3.6 TMN naming and addressing . 38 3.6.1 Principles for naming schemes . 38 3.6.1.1 Unambiguous naming . 38 3.6.1.2 Name structure . 38 3.6.1.3 Application layer names . 38 3.6.2 Addresses . 38 4 The TMN physica
13、l architecture 38 4.1 TMN building blocks . 39 4.1.1 Operations System (OS) 39 4.1.2 Mediation Device IMD) . 39 4.1.3 Q Interface Adaptor (QA) . 39 4.1.4 Data Communication Network (DCN) . 39 4.1.5 Network Element (NE) 39 4.1.6 Work Station (WS) . 39 4.1.7 Relationship of TMN building block names to
14、 TMN function blocks . . 39 4.2 Interoperable interfaces . 40 4.3 Interfaces 40 4.3.1 Definitions of the standard interoperable interfaces 41 4.3.2 Q interface . 41 4.3.3 Finterface . 42 4.3.4 Xinterface . 42 4.3.5 Relationship of TMN interfaces to TMN building blocks 42 4.4 TMN protocol families 42
15、 4.5 Consideration of reference and physical configurations 43 4.5.1 Physical realisation of the q class reference configuration . 43 4.5.2 Communication functions . 44 4.5.2.1 DCN implementation examples . 44 4.5.2.2 MCF considerations 45 5 Detailed TMN architectural considerations 47 5.1 General 4
16、7 5.2 Operation systems 47 5.2.2 Physical OS configuration . 47 5.3 TMN data communication considerations . 49 5.3.1 Data communication network considerations 49 5.3.3 Message communication considerations . 49 5.4 Mediation 50 5.4.1 Mediation considerations . 50 5.4.2 Processes of mediation 51 5.4.3
17、 Implementation of mediation processes . 52 5.5 Network element considerations . 52 5.6 Q-Adaptor considerations . 53 5.7 Work stations 54 5.7.1 Presentation function 54 5.7.2 g functions . 54 5.8 TMN standard interfaces 55 5.1.1 Messaging availabilin/reliabilin/ . 47 5.2.1 Functional OS configurati
18、on . 47 5.7.3 f functions . 55 5.8.1 Qinterface 56 COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesPage 5 ETR 037:1992 5.8.2 Qinterface 56 AnnexA 57 A.l Planning and design considerations . 57 A.l.l Functions attributes 57 A.1.2 Functional characteri
19、stics 57 A.1.3 Critical attributes 58 A . 1.4 Protocol selection . 58 A . 1.5 Communications considerations . 58 A.1.6 TMN naming and addressing 58 A.1.6.1 Principles for naming schemes 59 A.1.6.1.1 Unambiguous naming . 59 A.1.6.1.2 Name structure 59 A.1.6.1.3 Application layer names 59 A.1.6.2 Addr
20、esses 60 Appendix A to Annex A: . 60 A.A.1 Tables of function attribute ranges . 60 A.A.2 References 64 Annex B: Examples of functional architectures 65 B.l Functional TMN hierarchy 65 B.2 The management layers of the architecture . 65 B.2.1 Element management layer 65 B.2.2 Network management layer
21、 66 B.2.3 Service management layer . 66 B.2.4 Business management layer 67 B.3 Value added services . 67 B.4 Interaction between TMNs . 67 Annex C: Configuration examples . 70 Annex D: Considerations for managing networks 76 COPYRIGHT European Telecommunications Standards InstituteLicensed by Inform
22、ation Handling Services3404583 0067386 949 Page 7 ETR 037:1992 Foreword This ETR introduces the Telecommunications Management Network (TMN) concept, defines its scope, describes the functional and information architecture and gives examples of physical architectures. It also provides a functional re
23、ference model and identifies concepts necessary to support the TMN architecture. ETSI Technical Reports (ETRs) are informative documents resulting from ETSI studies which are not appropriate for European Telecommunication Standard (ETS) or interim European Telecommunication Standard (I-ETS) status.
24、An ETR may be used to publish material which is either of an informative nature, relating to the use or application of ETSs or I-ETSs, or which is immature and not yet suitable for formal adoption as an ETS or an I-ETS. Previous page is blank COPYRIGHT European Telecommunications Standards Institute
25、Licensed by Information Handling ServicesW 3404583 O067387 885 Page 9 ETR 037:1992 Introduction This ETSI Technical Report (ETR) presents the general architectural requirements for a Telecommunications Management Network (TMN) to support the management requirements of administrations to plan, provis
26、ion, install, maintain, operate and administer telecommunications networks and services. Within the context of the TMN, management refers to a set of capabilities to allow for the exchange and processing of management information to assist administrations in conducting their businesses efficiently.
27、IS0 systems management services and protocols represent a subset of the management capabilities that can be provided by the TMN and that may be required by an administration. The term administrations used in this document includes Registered Private Operating Agencies (RPOAs), public and private (cu
28、stomer and third party) administrations and/or other organisations that operate or use a TMN. A TMN provides management functions for telecommunications networks and services and offers communications between itself and the telecommunications networks and services. In this context a telecommunicatio
29、ns network is assumed to consist of both digital and analogue telecommunications equipment and associated support equipment. A telecommunications service in this context consists of a range of capabilities provided to customers. The basic concept behind a TMN is to provide an organised architecture
30、to achieve the interconnection between various types of Operations Systems (OSs) and/or telecommunications equipment for the exchange of management information using an agreed architecture with standardised protocols and interfaces. In defining the concept it is recognised that many administrations
31、have a large infrastructure of OSs, networks and telecommunications equipment already in place, and which must be accommodated within the architecture. It is also recognised that provision must be made for access to and display of management information contained within the TMN. Within the architect
32、ure there is no presumption that the management information user will necessarily be a human or that the mechanism by which the management information will be displayed is necessarily a workstation. The external interface could also be to other interfaces such as an alarm display or bell, and the ul
33、timate user of the management information could be an expert system. This ETR will provide both administrations and manufacturers with a set of standards to use when developing equipment, and when designing infrastructure for the management of telecommunications networks and services. Relationships
34、of a TMN to a telecommunications network: - a TMN can vary in size from a very simple connection between an OS and a single piece of telecommunications equipment to a complex network interconnecting many different types of 0% and telecommunications equipment; - a TMN may provide management functions
35、 and offer communications both between the 0% as such, and between OSs and the various parts of the telecommunications network. A telecommunications network consists of many types of analogue and digital telecommunications equipment and associated support equipment, such as transmission systems, swi
36、tching systems, multiplexers, signalling terminals, front-end processors, mainframes, cluster controllers, f ile servers, etc. When managed, such equipment is generically referred to as Network Elements (NEs); Previous page is blank COPYRIGHT European Telecommunications Standards InstituteLicensed b
37、y Information Handling Servicesm 3404583 ClClhi388 i11 m Page 10 ETR 037:1992 - figure 1 shows the general relationship between a TMN and a telecommunications network which it manages. A TMN is conceptually a separate network that interfaces a telecommunications network at several different points t
38、o sendheceive information to/from it and to control its operations. A TMN may use parts of the telecommunications network to provide its communications. This will be a requirement for the management by the TMN of the TMN network. 1 Scope This ETR identifies functionality, as function blocks, in so f
39、ar as they potentially delineate the interfaces, which are the subject of standardisation. Functional components are introduced to aid the understanding of how function blocks support the interfaces. These functional components are informally defined and are not subject to standardisation. 1.1 Field
40、 of application The following are examples of the networks, telecommunications services and major types of equipment that may be managed by the TMN: public and private networks, including ISDNs, mobile networks, private voice networks, VPNs and INS; TMN itself; transmission terminals (multiplexers,
41、cross connects, channel translation equipment, Synchronous Digital Hierarchy (SDH), etc.); digital and analogue transmission systems (cable, fibre, radio, satellite, etc.); restoration systems; operations systems and their peripherals; mainframes, front-end processors, cluster controllers, file serv
42、ers, etc.; digital and analogue exchanges; area networks (WAN, MAN, LAN); circuit and packet switched networks; signalling terminals and systems including signal transfer points (STPI and real time data bases; bearer services and teleservices; PBXs, PBX accesses and user (customer) terminals; ISDN u
43、ser terminals in accordance with relevant maintenance procedures in M.36 and 1.602 for public networks; software provided by or associated with telecommunications services, e.g. switching software, directories, message databases, etc.; software applications running within mainframes, etc. (including
44、 applications supporting TMN); associated support systems (test modules, power systems, air conditioning units, building alarms systems, etc.). COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services3404583 0067387 b58 = Page 11 ETR 037:1992 . In addition,
45、a TMN may be used to manage distributed entities and services offered by grouping of the items in the above list. All the equipment, applications software and networks or any grouping of equipment, applications software and networks described above, as well as any services derivable from any combina
46、tion of the above examples, will from now on be referred to as belonging to the telecommunications environment. WS = Workstation (-1 More complex network terminals like PABXs are not excluded from the TMN field of application Figure 1 : General relationship of a TMN to a telecommunications network C
47、OPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesH 3404583 0067390 37T H Page 12 ETR 037:1992 1.2 Basic objectives for the TMN The objective for the work on the TMN specifications is to provide a framework for planning the development of communications
48、 means for telecommunications management. By introducing the concept of generic network models for management, it is possible to perform general management of diverse equipment using generic communications interfaces. The principle of keeping the TMN logically distinct from the networks and services
49、 being managed introduces the prospect of distributing the TMN functionality for centralised or de-centralised management implementations. This means that from a number of management nodes operators can perform management of a wide range of distributed equipment, networks and services. Security and distributed data integrity are recognised as fundamental requirements for the definition of a generic architecture. A TMN may allow access and control from sources considered outside the TMN (e.g. inter-TMN co-operation and network user access). Security mechanisms may be needed at various levels (
